Fediverse

This is exactly the dynamic the article was describing: concerns about power concentration get answered with lists of theoretical protocol features instead of engaging with how the network actually operates. Listing technical escape hatches doesn’t address who controls the dominant infrastructure in practice.

The overwhelming majority of users rely on hosted PDSes, the main relay, and the default appview. Whoever controls those layers controls visibility, discovery, moderation signals, and reach. That’s where practical power sits. Doesn't matter whether migration is technically possible under ideal conditions because if you'll need it they won't be ideal.

Acquisitions and policy changes can happen quickly. Tools that exist “yesterday” are irrelevant if users don’t act before control consolidates, and history shows that most don’t. Claiming decentralization can wait until the last possible moment ignores how network effects and defaults entrench power long before any formal lock-in occurs.

It’s also worth noting that the original article isn’t even arguing “the fediverse is better,” yet the response immediately reframes the debate as a comparison. Even if we entertain that framing, the situations aren’t symmetrical. Yes, a fediverse instance can block migrations or misbehave but no single party in the fediverse comes close to the infrastructural dominance Bluesky Corp currently holds across relays, appviews, and user gravity. An individual Mastodon instance misbehaving affects its users. Bluesky Corp fully controls the experience of over 99% of the users on the protocol and so holds the power to shape the experience of the entire network.

The issue isn’t whether both systems have theoretical weaknesses. It’s where systemic leverage concentrates in practice. And ATProto’s architecture, particularly the cost and complexity of running the more demanding components that need to have a global view of the network, structurally favors concentration at those layers.