Earlier quoted context omitted.
"Only viable instance" is not really the correct framing - Bluesky doesn't have instances . Anyone using ATProto without Bluesky will still be "on Bluesky". When you go to bsky.app, you're interacting with the Bluesky AppView ; one key feature of ATProto is that any AppView can interact with any (consenting) Personal Data Server (PDS). So you can self-host your PDS but still use bsky.app if you so choose. But critica…
The nightmare of the Wsocial rollout is a testament of the massive control Bluesky has on the ATProto network. If Wsocial was on ActivityPub or Nostr nothing similar would have happened. ATProto has serious centralisation problems, baked into the design. And it makes sense, considering it came out of a Twitter R&D experiment to "decentralise" Twitter itself. Pure federation was never part of the initial design. Activ…
- many people wish they could control what they see and who they talk to. (Eg control the algorithm, avoid censorship from big tech)
- some people care about owning their data so it doesn’t go away when a company fails
- technical people are interested in building more types of social apps that aren’t just twitter posts etc
- nearly everyone just wants a fairly seamless experience without a lot of gotchas or technical problems to solve like self hosting an instance for your friends that falls over if too many people use it and is tricky to network with others.
Bluesky is trying to solve all those kinds of problems, which I think is pretty interesting, and I don’t think the others are quite doing the same thing technically. At the end of the day they are all pretty niche.