for permissioned spaces, records are light and easy to move out of a space, but blobs are heavy. what if blob visibility was derived? a blob stays confined to its space until a public record references it. deleting the public record would make the blob only available to the space again.
Aug 19, 2026 at 4:25 AM
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.
Permissioned Data Shapes: Private Events - Nick's Blog
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
A self-only space is the smallest shape permissioned data can take: one authority, one member, one repo, and private bookmarks that share a record shape and a write path with public ones.
Blob store design challenges
It's just hashed data, what's so complex about a blob store anyway?
Spaces as Layers - Nick's Blog
Public anchor records paired with sidecar records in permissioned spaces give ATProtocol apps a composable pattern for blending open discoverability with controlled access.
Nonrivalry and the Economics of Data
(September 2020) - Data is nonrival: a person's location history, medical records, and driving data can be used by many firms simultaneously. Nonrivalry leads to increasing returns. As a result, there may be social gains to data being used broadly across firms, even in the presence of privacy considerations. Fearing creative destruction, firms may choose to hoard their data, leading to the inefficient use of nonrival data. Giving data property rights to consumers can generate allocations that are close to optimal. Consumers balance their concerns for privacy against the economic gains that come from selling data broadly.
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
Oauth scopes vs record permissions
i hope this is an alright place to put this, but it was just a thought i had inspired by this tweet even with oauth scopes, i think that interoperability between applications is a tough problem because i have to fully trust every oauth client that i use with access to record namespaces. so if i have existing bluesky records, and then i want to use a different application which wants to be able to create and delete bluesky records, either i can’t use bluesky features in that application, or i ne...
What if permissioned data but then public though
Transitioning data from permissioned to public?
discourse.atprotocol.communityA 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.pub@dholms.at thinking about permissiones data. What if: Permissioned data URI was at://<PDS did>/<record type>/<rkey> exactly the same as public data. The PDS would handle the space assignment opaquely and do a 4xx response with some space aturis. Client goes and grabs a space cred and retries
There is one area with Permissioned Data Spaces that I haven't seen discussed. It reveals that data is currently stored in the (I think I'm coining a term here) *Public Space* on Personal Data Servers. Remember, most people on Bluesky aren't aware of where their data is stored, or what that means.
Is this a thing? Something about private data on AT Proto, where a person could purchase content and have a copy of said content injected into their Private Data, so it could not be removed without their consent? I’m thinking “I’ve bought a copy of a book, and now the book blob lives in my PDS”
The smallest permissioned data shape: a bookmarks space with a member list that never grows past me. Same bookmark record the atmosphere already uses, same write path, different address. URIs, scopes, tokens, and the full credential flow inside.
Permissioned Data Shapes: Self-Only Bookmarks
ngerakines.leaflet.pub
