ATProto adds private data spaces, decentralized stack matures
The AT Protocol published a proposal for 'Spaces,' a mechanism for non-public data on the Bluesky-native decentralized protocol. The HN discussion immediately noted that tangled.sh is likely to use this for private repos, suggesting the developer tooling community is already watching ATProto as infrastructure, not just a social network substrate. Commenters also pushed back on the naming: 'Spaces' sounds like live audio rooms, not access-controlled data scopes.
The pattern: ATProto is quietly becoming a more general-purpose decentralized data protocol, and the additions that matter most are not user-facing features but plumbing. Private data is the thing that was always missing from federated and decentralized systems, and solving it correctly without recreating centralized auth is genuinely hard.
The 'so is this now just, like, a server?' comment in the thread captures a real tension: the more capability you add to handle private data, the more it starts to look like a traditional server with extra steps. That is not necessarily bad, but it is worth naming.
So what?
Founders building on federated or decentralized infrastructure should watch this closely. Private data handling is where most decentralized stacks have historically punted, and ATProto is attempting to solve it at the protocol level. If they get it right, it opens up a much wider category of applications than public social data.