Bluesky Is Not Decentralized

Original Article ↗ Hacker News Discussion ↗

Bluesky’s Decentralization Model (AT Protocol & DID PLC)

  • Supporters describe AT Protocol as “web-like”: each user is a host, apps are aggregators/search engines.
  • Critics focus on the DID:PLC registry at plc.directory, resolved via a centralized web service, as a core centralization point.
  • Some argue moving DID:PLC to an ICANN-style nonprofit would be acceptable; others note ICANN is still centralized and worry once a single directory is standard, alternatives become impractical.
  • Today the directory choice is compiled into clients, not exposed as an easy preference, though open source allows forks.

Self-Hosting, Portability, and Failure Modes

  • Bluesky offers Personal Data Servers (PDS) and documented self-hosting; self-hosted accounts can interact with others.
  • A PDS is an independent store of a user’s data; if bsky.app vanished, a user could, in principle, run their own app stack on top.
  • Caveat: an alternative directory must exist and other clients must recognize it, otherwise identity resolution breaks.
  • Compared with Mastodon, where an instance can run fully independent of any flagship server, some see Bluesky as more brittle.

Algorithms and Feeds

  • Participants clarify Bluesky never promised “no algorithm”; instead, it promotes user-selectable, open recommendation services.
  • There’s extensive debate over the word “algorithm”: some use it broadly (even chronological sorting), others reserve criticism for engagement-optimizing, opaque recommender systems.
  • Many want user control and transparency over ranking, not an absence of computation.

Comparisons: Mastodon, Threads, X, Nostr

  • Mastodon: praised for federation and quieter, niche communities; criticized for poor UX, hard migration of posts, limited global search, and social friction between servers.
  • Threads: its ActivityPub integration is seen as mostly one-way and limited so far.
  • X/Twitter: some say it has added features but degraded moderation, stability, and public accessibility; others disagree on how “broken” it is.
  • Nostr: viewed as very decentralized but with painful UX (manual key management).

Federation vs. Decentralization and Governance Concerns

  • Ongoing argument over whether federation “counts” as decentralization or merely shifts power to many server operators.
  • Some see Bluesky as moderately decentralized with the potential for much more if DID:PLC governance is reformed.
  • Others worry about capture: Bluesky’s VC funding, board composition, and dominance of its own PDS/relay raise concerns about future enshittification or slow‑walking protocol features.