Infrastructure August 24, 2026 mixed ⇧ 150 pts across 1 thread

ATProto adds private data spaces, Bluesky ecosystem matures

AT Protocol shipped a spec for 'Spaces,' a new extension enabling non-public data on a protocol that has been entirely public by design until now. The HN thread is short but pointed: one commenter simply asks 'So is this now just, like, a server?' which is a fair challenge to whether this is a meaningful protocol innovation or just rediscovering what servers already do. Another comment notes that tangled.sh is about to get private repos, signaling that the ecosystem is already building on top of the extension before it's fully specified.

The naming confusion (Spaces colliding with live audio connotations from Twitter/X) is a minor but real issue for adoption. More interesting is that the extension represents ATProto trying to become a general-purpose decentralized app substrate rather than just a public social graph protocol. That's a significant scope expansion.

The question the thread doesn't fully answer is whether the federation model survives the addition of private data cleanly, or whether private data creates new coordination problems that the public-only design avoided.


So what?

If you're building on ATProto or watching the decentralized social space, this is the moment where the protocol either grows into a real platform or gets complicated enough to lose its architectural clarity. For founders considering decentralized infrastructure, the private data question is now answered in principle, which removes one blocker for building consumer apps with any expectation of user privacy.

Read these