HappyFrog@lemmy.blahaj.zone
on 18 Aug 14:23
collapse
It’s not decentralized though. The way it’s written requires you to host everything in bluesky along with everything on your own instance to be fully autonomous. That makes it impossible for normal people to host it.
irelephant@lemmy.dbzer0.com
on 17 Aug 22:42
collapse
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.
airportline@lemmy.zip
on 17 Aug 12:31
nextcollapse
I actually still don’t understand why one would be in favor of federation but opposed to bridging. In esscence, bridging is just federation.
fmstrat@lemmy.nowsci.com
on 17 Aug 16:35
nextcollapse
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.
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.
A_Chilean_Cyborg@feddit.cl
on 18 Aug 14:03
collapse
Seeing these comments, is true what they say, people want these spaces to be their nerdy little corners, instead of technology made to actually defy big tech LMAO.
threaded - newest
My condolences to them.
Why?
Not a fan of BlueSky and their proprietary platform
The AT protocol is open, though
So is the rest of it lmao
It’s not decentralized though. The way it’s written requires you to host everything in bluesky along with everything on your own instance to be fully autonomous. That makes it impossible for normal people to host it.
Bluesky is open source.
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.
I actually still don’t understand why one would be in favor of federation but opposed to bridging. In esscence, bridging is just federation.
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).
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
Ok, maybe found a new reason. I’m not sure how the binding arbitration would work going through a bridge.
…
Source: pluralistic.net/2025/08/15/dogs-breakfast/#by-cli…
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.
Fcuk buesky
Seeing these comments, is true what they say, people want these spaces to be their nerdy little corners, instead of technology made to actually defy big tech LMAO.