Quietly this year, the protocol under Bluesky started leaving Bluesky. The IETF chartered a working group, "Authenticated Transfer Protocol", to standardise atproto's core. Worth understanding what that does and, more importantly, what it doesn't. 🧵
---
What it changes is governance. The repo format, the sync protocol, the at:// URI scheme: these move from Bluesky's reference implementation to vendor-neutral IETF specs. Bluesky's own framing is that the core protocol gets "a home outside of and independent from Bluesky PBC."
First caveat: this is early. The deliverables are Internet-Drafts, not finished RFCs. An I-D is a working document: it can change completely or expire. The charter was approved in early 2026; the actual standards are a multi-year job. "Standardised" is the destination, not the current state.
Second caveat: it's narrow. In: repository structure, sync, the at:// scheme, account-identifier resolution. Explicitly out : private data, the app.bsky lexicons, and the whole labeling/moderation system. The parts you actually feel as a user remain Bluesky-driven. For now.
Also the live network still leans on one company. Main relay, primary AppView, did:plc, the default PDS — all Bluesky PBC. You can self-host every piece, but the defaults are theirs. The architecture is decentralised; the network isn't yet. Does standardizing the specs actually change that?
I have high hopes for the at-proto. I’m actually hosting my own PDS so my data is hosted by me and authenticated by me. I also anchor my identity with my domain name, geofox.org, with a did:web, instead of relying on Bluesky’s Public Ledger of Credentials (that governance is actively being moved out to an independent association).
That domain is linked to my identity for years, so it was the logical choice. I’ve published a bit more info on my blog : geofox.org/posts/decentralized-social/#bluesky--at-protocol-my-data-my-domain-my-did
On the other side of the social spectrum, Meta's ActivityPub support on Threads isn't openness, it's an alibi. Federation is opt-in, buried, and one-way for everything that matters: your replies and graph don't come with you, so there's no door out, only a window in. They adopted the wire format and skipped the portability, the one part that would actually let users leave. That's not interoperability but a compliance gesture dressed as principle, shipped by the company with the most to lose if it were real.
Sources: IETF charter (Authenticated Transfer Protocol WG) datatracker.ietf.org/doc/charter-ietf-atp/ · Bluesky's announcement atproto.com/blog/kicking-off-the-atp-working-group
