Hey all 👋🏼, Anuj here from @anewsocial, the organization that manages Bridgy Fed.
We recently added a new feature to Bridgy Fed that folks have asked us for [1] - an easy way for admins to automatically bridge their new users and give them custom domain handles on Bluesky. We wanted to take a moment to explain the philosophy behind it, and how we’re trying to do this the right way, keeping consent front-of-mind. 1/10 🧵
For instances that already have a user base, admins should not make any significant decisions without the consent of their users. This goes against our values, and we will not permit an instance to use Bridgy Fed in this manner. We’ve had conversations on how to handle a situation like this, and we would block instances [3] from doing so. We strongly expect admins to be loud about bridging, especially during signup. 3/10
This is very encouraging to read from a project that initially did not understand why many would be opposed to an opt-out bridge to ATProto.
Ok, maybe found a new reason. I’m not sure how the binding arbitration would work going through a bridge.
Without the ability to participate on the Bluesky network without having to create an account with Bluesky (the company), users would have to subject themselves to Bluesky’s terms of service, and could have their access to the Bluesky network unilaterally terminated by Bluesky (the company).
…
As things stand, Bluesky has very bad terms of service that every user who creates an account has to subject themselves to. In particular, Bluesky’s ToS contain a “binding arbitration” waiver that forces users to surrender the right to sue Bluesky no matter how the company harms them.
There is no principal problem with bridging to another open system, but Bluesky is not. This is no different from federating with Meta’s Threads, which most people on the Fediverse seem to be against as well.
This is very encouraging to read from a project that initially did not understand why many would be opposed to an opt-out bridge to ATProto.
Yep. Ryan (the only BridgyFed dev at the time) really did absorb the feedback and changed direction, and Anuj also gets the importance of consent.
I actually still don’t understand why one would be in favor of federation but opposed to bridging. In esscence, bridging is just federation.
Ok, maybe found a new reason. I’m not sure how the binding arbitration would work going through a bridge.
…
Source: https://pluralistic.net/2025/08/15/dogs-breakfast/#by-clicking-this-you-agree-on-behalf-of-your-employer-to-release-me-from-all-obligations-and-waivers-arising-from-any-and-all-NON-NEGOTIATED-agreements
There is no principal problem with bridging to another open system, but Bluesky is not. This is no different from federating with Meta’s Threads, which most people on the Fediverse seem to be against as well.
I think bluesky has more goodwill than meta by a loooong shot, though we’ll see if it lasts as more attempts to monetize it are made
Unless I’m misunderstanding: One-way bridging.
That’s very different from Federation.
It’s two way bridging. The issue is that Bluesky users also must opt-in to having their posts be bridged to Mastodon (by following @ap.brid.gy).