ATProto Permissioned Data Proposal Draft

Bluesky’s latest proposal is basically a very early sketch for how private or restricted data might work on its network, and the author is practically waving a giant caution sign: please don’t get too attached yet. Even Dan Abramov jumped in to repeat the warning that this draft will likely change. But of course, telling the internet not to overreact is the fastest way to make everyone do exactly that.

The comments quickly turned into a mini soap opera of optimism vs. suspicion. One camp immediately saw shiny new possibilities, with one user asking if this could mean private code projects on Tangled. Translation for normal humans: people instantly started dreaming up locked-door spaces where only approved members can see what’s inside. That’s the hopeful version.

Then came the skeptical crowd, and this is where the drama kicked in. Another commenter zoomed in on what they saw as an awkward power balance: storage spread out across users, but permission checks handled by a central gatekeeper. In plain English, critics are worried this could still leave one big bouncer deciding who gets in. Even juicier, they suggested apps may end up copying everything anyway, which takes some of the shine off the “private but distributed” pitch.

So the vibe is classic early-tech-thread chaos: half the room is already building castles in the air, while the other half is asking who really holds the keys. No memes exploded here, but the underlying joke was unmistakable: this is “just a draft,” and yet everyone is already arguing about the future like it ships tomorrow.