- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Bridgy Fed’s Bluesky integration is now in beta, and makes it possible to connect your account from the Fediverse to Bluesky, and vice versa.
There’s still some quirks, and every bridged account has to opt in to it, but it’s a promising moment for people that want to communicate across networks.
Come now Sean, you know that everything open about BlueSky is smoke and mirrors, considering that everything stops and starts with the indexer.
Isn’t that the same issue with ActivityPub and the instances that host accounts and messages?
No. With ActivityPub, it’s totally decentralized. There’s no central authority whatsoever. What there is however, is an instance that’s bigger than the rest. So if we talk about Lemmy. I can access it and post and my ISP can block Lemmy World and I’d never know.
With BlueSky, it pretends to be similar, but the reality is that everything needs to go through their central server in order to be displayed on a timeline. BlueSky is designed in such a way so that everyone does the heavy lifting, but to be seen, you need to have approval from their central server, where they can modify, insert adverts, do whatever. It’s a centralised service that cosplays as decentralised. I don’t understand why people keep pushing it when it’s literally the same shit we all escaped from but with a new paint job.
I’ll tell you why I signed up. Because I’m a non-techie, and didn’t KNOW any of that.
I can’t tell whether this is serious or sarcastic 😅
As far as the “global square” part of the equation is concerned: yeah, you’re right! A firehose of public statuses requires indexing to work, as a basic foundational premise.
However, there’s nothing preventing someone from standing up a PDS, opting out of the firehose / big graph service, and instead leaning on federation between individual PDSes. I’m not saying it would necessarily be a common use-case, but it’s definitely not impossible.