I've had a lot of people ask how BlueSky compares to Mastodon and the Fediverse. I've tried to make the answer as simple and easy to understand as possible:
BlueSky is designed to give corporations and wealthy people full control of the network. All of its traffic has to flow through expensive-to-run corporate relays.
The Fediverse is designed to give ordinary people control of the network. All of its traffic flows directly from one cheap-to-run server to another.
@FediTips@social.growyourown.services
I still think Christine Lemmer-Webber's blog post on it is a worthwhile read for people a little more technical.
https://dustycloud.org/blog/how-decentralized-is-bluesky/
@o76923@kitty.social @FediTips@social.growyourown.services I also think it’s important to specify something.
The Fediverse is designed to give ordinary people control of the network. All of its traffic flows directly from one cheap-to-run server to another.This is only partially true. In bluesky the way it works is that you have to be connected to the relay. Posts must be "published" to the relay and while you can get a slice of the relay with an appview it still has to connect to the relay. This is something that is expensive to run and manage. Fedi works a bit differently because not every instance is talking to each other. If I follow someone on mastodon.social I am going to get their posts, not the entirety of mastodon.social’s traffic.
Not strictly true.
ATProto allows relays to be optional—appviews could subscribe directly to PDSs.
But it reduces connections, which allows a relay in ATProto to run a fraction of the cost _per user_, even where the aggregate cost is higher (I think one estimate from a while back is that it is on the order of millions or tens of millions of BlueSky users for about the cost of Hachyderm).
AP is also, as implemented rather than as designed necessarily, _hellishly_ expensive per user compared to pretty much every major systems protocol.