In which I retcon the naming of everything.
Modeling communities on permissioned data - Daniel's Leaflets
Arguing against "universal spaces" and raising a couple questions that come up as a result.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Permissioned Data Diary 4: The Big Picture - Daniel's Leaflets
A special edition of the data diary that sketches out the rough shape of where we're heading.
Permissioned Data Diary 6: Boring Auth - Daniel's Leaflets
In which we resist the temptation to invent a clever authorization model & pick the boring one instead.
Reintroducing Spaces - Daniel's Leaflets
Zooming out and re-motivating the design of spaces, the new primitive for non-public data on atproto.
Reintroducing Spaces - Daniel's Leaflets
Zooming out and re-motivating the design of spaces, the new primitive for non-public data on atproto.
Reintroducing Spaces - Daniel's Leaflets
Zooming out and re-motivating the design of spaces, the new primitive for non-public data on atproto.
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.
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 by dholms · Pull Request #94 · bluesky-social/proposals
This is an initial proposal for permissioned data. Details, terminology, and behaviors are all likely to change. For a friendly introduction to the protocol, check my my Leaflets. For discussion, f...
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 PDS Lexicons
I wanted to share a first pass of the PDS lexicons for the permissioned data protocol to get some feedback while the paint’s still wet! You can check them out on my working branch: Comparing main...permissioned-data · bluesky-social/atproto · GitHub They’re all under the com.atproto.space namespace: atproto/lexicons/com/atproto/space at permissioned-data · bluesky-social/atproto · GitHub Confidence rating on Lexicons is probably like ~70-80%. Broad strokes, I think the shape is there. Though ...
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
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.
Spaces explainers
Search terms: AT Protocol Spaces, ATProto Spaces, permissioned data, buckets
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
The Atproto Spaces Alpha is Live - AT Protocol
Reintroducing Spaces - Daniel's Leaflets
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
