How this works, and what it does with your credentials
- No backend. Your browser talks directly to
bsky.socialand your Mastodon instance's API — we never see or log your credentials. - Nothing is stored. Your password and token live only in this tab's memory and vanish on refresh.
- Read-only. We only read your two follow lists and show the difference — never follow, unfollow, or post.
Don't take our word for it — read the source on GitHub.
How does the matching work?
- Handle convention. Bridgy Fed bridges accounts using a predictable handle, e.g. Bluesky's
alice.bsky.socialbecomes@alice.bsky.social@bsky.brid.gyon the fediverse, and vice versa. We first check whether your other follow list already contains that exact bridged account. - Fuzzy fallback. If no account matches that convention, we look for a follow with the same display name or a shared link/domain in the bio, in case the account bridged under a different handle (e.g. a custom domain).
- Live bridge check. Anything still unmatched gets a live webfinger/handle lookup against Bridgy Fed to see whether a bridge account actually exists on the other side yet. If it does, it lands in one of the "Follow on…" columns below. If it doesn't — or the lists are too large to check live — it lands in Unmatched / unbridged.
🐘 Follow on Mastodon
Followed on Bluesky, not detected on Mastodon. Links open your instance's follow-confirmation page for the Bridgy Fed bridge account.
No gaps found — you're following the bridge for everyone here.
🦋 Follow on Bluesky
Followed on Mastodon, not detected on Bluesky. Links open the Bridgy Fed bridge account's Bluesky profile.
No gaps found — you're following the bridge for everyone here.
Unmatched / unbridged
No Bridgy Fed bridge could be confirmed for these accounts on either side. They might not have bridged yet, or might use a setup this tool doesn't recognise — worth checking manually.
None — every follow was matched or bridged.