Post

So yeah, like I was rambling out the other day, we basically have confirmation that self-hosting doesn’t equal sovereignty. Even if you run your own PDS, the app layer remains the choke point. Bluesky proper (or any other dominant client) can quietly choose not to surface your content.

ændra and others are circling this in the thread this came from, but IMO they’re all still thinking in old-school federated terms, where blocking a whole server is the nuclear option. I would argue that the actual dynamic now is subtler and prone to more shenanigans.

If I had to sum up: decentralization isn’t freedom if discovery and aggregation remain centralized; having your own PDS will simply make you the proud owner of a private ghost town unless the central graph decides you’re worth routing.

Independence would require multiple competing ingestion layers, not a scattering of self-hosted servers beneath one central arbiter. Basically, the issue isn't hosting; it's routing. Who controls the map decides whose voice is audible. ATProto doesn't evne CONCEPTUALLY engage with this problem.

ATProto solves for identity portability and data sovereignty at the account level, which is effectively all storage layer. It doesn't consider and never addresses the attention layer, which is where the actual power dynamics manifest. I mean, it's the Maginot Line problem in protocol form.

The risk now becomes that Bluesky doesn't need to delete you, they just stop indexing you or quietly downrank you in the trust graph. Which, yeah, is less of a problem for established media types, so a journalist PDS might be "safe" because they're primed to notice this anyway.

In focusing entirely on data ownership, ATProto built a fortified wall where the fight used to be. It solves some of these issues pretty well! But the actual battles are now happening in the terrain of feeds and discovery, and next federation policy as people explore their options.

These are areas it treats as neutral plumbing rather than political space. I don't think you really solve this with any one trick. You have to pluralize the attention layer and make exclusion expensive, visible. Competing aggregators.