I really worry that permissioned data is gonna kill a lot of stuff Take my recipe app: If i wanted no one to have access to the records but my app all i have to do is 1. create a space 2. use that space for all user content Bam, now no open data
Jul 20, 2026 at 4:58 PM
Permissioned Data: Space Access - Nick's Blog
Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
Permissioned Data Diary 3: Your Bucket, My Data - Daniel's Leaflets
The third in a series of posts building up a solution to permissioned data on atproto. We look at two different models for where buckets live and why the simpler-looking one doesn’t work out.
Permissioned Data Diary 2: Buckets - Daniel's Leaflets
The second in a series of posts building up a solution to permissioned data on atproto. We introduce buckets: a new protocol primitive for creating a shared social context.
Permissioned data is a love triangle - Nick's Blog
Permissioned data is a love triangle between the user, the identities they grant permissions to, and the applications everyone uses to view controlled data. We don't need to change or reinvent the protocol to have it, because ATProtocol already supports it.
Permissioned Data Shapes: Notifications - Nick's Blog
A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.
Permissioned Data Shapes: Feeds - Nick's Blog
Public feed generators drink from a firehose that permissioned data never enters, so a feed that includes space content has to become a syncer, keep a live model of who can see what, and serve a different skeleton to every viewer.
Permissioned data on atproto — pick your depth
A private room in a place with no walls: how engineers are adding permissioned data to atproto. Read it plain-language or technical.
B-Sides: Permissioned data is a love triangle - Nick's Blog
This is a B-sides post with unpolished thoughts that didn’t make it into the main article.
A deep dive on permissioned-data space access. The dials, policies, and the difference between handing out keys and revoking them.
Permissioned Data: Space Access
ngerakines.leaflet.pubThe key questions: how much power will apps be given to determine and enforce what data is permissioned? What incentives will apps have to make any data public? So far the protocol has been a forcing function for (adversarial) interop. We need to be intentional about not recreating app silos.
daniel holmgren 🫠
hey we're really working on permissioned data! read the first in a series of posts i'll be doing about our design decisions along the way. this one is about our decision to not do an e2ee system
What if permissioned data but then public though
Transitioning data from permissioned to public?
discourse.atprotocol.communityThe #atproto AppView I've been working on needs to store more and more private data. However, I don't want to wait for Spaces to be ready. I'm gonna need to do some data migrations once Spaces land 😅
new data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)
Permissioned Data Diary 5: What’s in a Name?
dholms.leaflet.pub
