Bluesky, decentralisation, and the distribution of power Bluesky has seen a large inflow of new users following the results of the US election, and a significant amount of media attention as well. All that attention to Bluesky has also led to a renewed conversation around the question of whether Blu...
You can host your own PDS (making it distributed but not decentralized), there is an ability to host a relay but hosting a relay requires mirroring the entire network instead of just subscribed nodes like AP, making it cost prohibitive for communities to organize their own relays on ATProto.
If bluesky is serious about decentralization then they need to make mirroring the entire network optional, allow relays’ firehoses to only to stream the activity from subscribed accounts from their users and federate with relays that don’t mirror the entire network.
Mirroring the entire network is what makes it a friendly experience for newcomers, IMO. In my own Mastodon instance I have to subscribe to a big relay (infosec.social) so that a reasonable proportion of replies from other instances I don’t happen to be happening populates into the feed.
I suppose you could say AP makes this optional, but that seems like a reasonable design choice to diverge on rather than a critical flaw in my opinion.
I don't really get all the pessimism. Even if folks are right in saying there'll be a bait and switch, this is people moving to a new platform en masse. If Bluesky goes to shit there's more reason to believe users would just move again.
In the meantime, as members of the fediverse, we should be using Bluesky being "decentralized" as a way to ease people into actually decentralized platforms.
I can tell you right now nobody's on Bluesky because it's "decentralized" because the evidence is clear, it's not in practice decentralized lol.
This is all a bloody waste of time. I really wish I could just fast-forward two years into the enshittification when everyone realizes they got duped by Big VC. Again.
host your own PDS, where your account lives, this is easy, I do it myself already.
host you own appview: the only actually good appview is bsky's, luckily it's open source, unfortunately I do not believe they made it easy to self-host.
Host a relay, this isn't all that hard, it just needs a real big server (AFAIK it needs a shitton of io throughput), so unless you're very rich it's not too realistic to host this.
So yeah, a PDS is easy to host but the other two parts are a pain, and since the protocol has only been open for a few months, people haven't really done too much.
Frontpage exists, but they haven't made it be able to interact with bsky.Social, although the accounts are shared. I have been told by people involved with that that that's an issue with frontpage's implementation, and not the AT protocol
Their PDS is self hosted, but it does still rely on the central relays (though you COULD host that yourself if you wanted to pay for it, I suppose?).
It's very centralized, but it's not that different from what you'd have to do to make Mastodon useful: a small/single user instance will get zero content, even if you follow a lot of people, without also adding several relays to work around some of the design decisions made by the Mastodon team regarding replies and how federation works for those kind of things, as well as to populate hashtags and searches and such.
Though really you shouldn't do any of that, and just use a good platform for discussion, like a forum or a threadiverse platform. (No seriously, absolutely hate "microblog" shit because it's designed to just be zingers and hot takes and not actual meaningful conversations.)
Just a hunch, but I think no decentralised network is going to run ATProto unless someone other than Bluesky forks it and makes the protocol changes that would allow that to be practical. I guess it's possible, in theory?
I'm not sure what approach would work. As I understand it, it's designed around the idea that all messages get routed through a monolithic "relay" which needs to see every single event from every user in order for any of them to get routed between the PDS nodes where user data gets stored.
Probably best to just add ActivityPub on top of it, if they really wanted to federate with anyone.
Decentralisation doesn't necessarily come with decentralized technical infrastructure, but its the basis for it. I'm still betting on ActivityPub. Sure social insentives are important, but the most openess will win. Also, Wordpress, Flipboard, Threads already joined ActivityPub, so the ecosystem already is kind of attractive in that direction.