Stoatcord

Stoatcord moves a Discord community onto Stoat, the open-source Revolt fork, and keeps both halves in sync while people finish leaving. The part worth looking at is the consent protocol. A Discord admin can't just point /migrate at somebody else's Stoat server: the bot posts an approval request into that server and the Discord slash command blocks on a promise until a Stoat admin with ManageServer replies approve, or five minutes run out. The alternative path is a one-time six-character claim code, crypto-random, consumed atomically, expiring in an hour, generated by an admin on the Stoat side — and it works in reverse too, a Stoat admin can push a migration request into Discord. Re-running a migration re-authorizes from scratch; there is deliberately no "already linked" shortcut.

Cloning the server means compiling one permission model into another. Twenty-four Discord permission flags become thirty Revolt bits, and the mapping isn't 1:1 — ManageRoles fans out to three separate Revolt bits, ManageWebhooks implies Revolt's masquerade bit, roles map allow-only while per-channel overrides carry independent allow and deny bitfields. Everything Stoat can't represent — slowmode, mentionable roles, role icons, over-length names — is collected into a warnings list and shown to you rather than dropped. --dry_run prints an itemized create/update/skip plan without touching either API, and include_snapshot posts a complete forensic record of the Discord server — every role, channel, permission overwrite, ban, pin, emoji and sticker — into a #migration-log channel, so you keep a readable copy of what you left.

Then it has to survive being on for a year. The live bridge carries messages, edits, deletes, reactions, typing and channel metadata both ways, with four separate echo-suppression sets on different TTLs because an edit you relay comes straight back as an event you must not relay again. Every message writes an ID-pair row, which is how an edit finds its counterpart months later. After a disconnect the bot diffs its last-bridged cursors against both platforms and replays the gap. And because Stoat's own WebSocket doesn't deliver other users' server messages to bot connections, there's a REST poller rotating ten channels every five seconds, synthesizing the events the platform won't send and dispatching them through the same handler as the real ones. Off to the side sits the push stack — FCM with RS256 service-account JWTs, plus VAPID WebPush and UnifiedPush behind an SSRF filter that blocks cloud-metadata addresses — which is the only reason the sibling Stoatally Android app gets notifications at all.