On Bluesky, your server operator holds the keys to be you
A breach of your data server merely leaks posts that were already public. But whoever holds your rotation keys can post, like, and follow as you — with valid signatures no one can tell apart from the real thing.
Roughly 99.9% of ATProto accounts sit on Bluesky's own servers and never register a backup rotation key. That single gap turns the operator into a custodian who can impersonate you across Tangled, Grain, and Leaflet, not just one app.
The theory said you would hold the private keys. The product decided otherwise, because making millions of people manage cryptographic material would have crushed signups.
The fix is unglamorous: make backup-key enrollment mandatory at account creation, baked into the client.
A breach you can shrug off, a key you can't
Kevin's argument in his post is that ATProto and Bluesky are "faux decentralized." The protocol theoretically lets you own your identity. In practice, the Personal Data Server (PDS) operator holds both your signing keys and your rotation keys — for nearly every account on the network.
What the operator can actually do as you
That custody is not a footnote. A PDS operator can post, like, follow, grant repo access, or permanently disable your identity, and the signatures are cryptographically indistinguishable from your genuine activity. Because ATProto identities travel across the whole ecosystem — Bluesky, Tangled, Grain, Leaflet — the hijack is ecosystem-wide, not app-local.
Kevin draws a sharp asymmetry. A PDS data breach exposes data that was already public, so it barely matters. Key control is the opposite: it enables full impersonation. And about 99.9% of users live on Bluesky's PDSes without ever registering a higher-priority backup rotation key, so they have no recovery lever if the operator turns. His fix is concrete: make backup rotation-key enrollment mandatory at account creation and build it into clients, instead of leaving it as an expert opt-in almost no one performs.
The thread tests the claim from both sides
The custody was a deliberate call, not an accident. As one veteran commenter put it, "You have the ability to move, as long as Bluesky Social PBC allows it. They hold the keys for your DID. … The original theory was that you'd hold the private keys, but that's something that would hugely limit adoption so they decided to hold the keys themselves."
"You have the ability to move, as long as Bluesky Social PBC allows it. They hold the keys for your DID. … The original theory was that you'd hold the private keys, but that's something that would hugely limit adoption so they decided to hold the keys themselves." — a commenter on the adoption-vs-sovereignty tradeoff
The most common rebuttal was "you don't own your domain either." A high-karma reader cut it down by naming what's different:
"Your domain name owner or DNS provider cannot redirect your domain name to a different server and cryptographically impersonate you." — Aurornis, 53k+ karma
The escape hatch exists; the trouble is that almost no one walks through it. A Cloudflare engineer who ships a hosting product offered one in a single line:
"You can host it for free on Cloudflare using my Cirrus PDS: https://cirrus.earth/" — ascorbic, dev tooling at Cloudflare
Kevin himself returned to reframe the whole thing as incentives rather than capability:
"When Bluesky goes rogue because of profitability issues or VC pressure, the vast vast majority of users lose their identities … Users will choose the path of least resistance." — the post's author, defending his thesis
Why "you can self-host" misses the point
The defense and the critique never actually collide, because they answer different questions. Yes, the path to true ownership is open. But a system where 99.9% of people take the default, and the default hands one company the keys to be them, is decentralized only on paper. The interesting fight in the thread is not whether sovereignty is possible — it's whether a protocol can claim to deliver it while engineering every incentive against people claiming it.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
A Bayer drug-research AI agent, and the 3.1/5.0 the article left out
Thirty paragraphs detail a multi-agent architecture orchestrating retrieval, reflection, and writing. Two paragraphs cover evaluation. The hard number — how well it meets user needs — appears only in a linked paper a commenter went and read.