Bluesky Risks Becoming Centralized Twitter

The real risk is strategic, not technical, because if Bluesky keeps most users, data hosting, and governance inside its own stack, the protocol stops looking like a new social network architecture and starts looking like a harder way to build Twitter. Bluesky already ships portable identity, custom feeds, and self hosted server tooling, but the ecosystem still depends heavily on Bluesky operated infrastructure, while the governance board that would signal broader control remains unestablished.

• Mastodon shows what visible decentralization looks like in practice. It runs across 13,000 community servers with 11M accounts, so users and developers can clearly see that the network is bigger than any one operator. That makes decentralization legible, not just theoretical.
  1 sacra
• Bluesky has opened important pieces of the stack. Official docs say federation on the live AT Protocol network and self hosted PDS support are available, and GitHub updates show newer auth features rolling out beyond bsky.social. But that is still different from broad third party usage at meaningful scale.
  2 bsky 5 bsky 6 github
• The competitive pressure is rising because Threads is adding fediverse features inside a much larger consumer app. Meta says Threads supports sharing to the fediverse, fediverse discovery, and a dedicated fediverse feed, which means open protocol language is no longer unique to Bluesky.
  1 sacra 7 fb 8 fb

The next phase is about making decentralization visible in the product and ecosystem. If more publishers, communities, and independent operators run their own AT Protocol infrastructure, Bluesky can become the default network layer for open social. If not, the market will treat it as a well designed microblog app with extra moving parts.