A forum with public categories, private categories, and one set of record shapes across both: members own their posts, the forum owns the submission wrappers that admit them into categories, and moderators deactivate into tombstones instead of deleting.
Permissioned Data Shapes: Community-Moderated Content - Nick's Blog
A community can own spaces the way a person does: a club's members post to each other under a dedicated community DID, with a feed space for content, a moderation space for notes, a labels space for filtering, and a single app view as the only window into any of it.
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.
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.
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.
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 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 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 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 Interlude: Spaces - Daniel's Leaflets
In which I retcon the naming of everything.
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.
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 Shapes: Polls - Nick's Blog
A poll is a space, a ballot is an address, and read_self is the ballot screen: voters cast and change their own votes while no voter's client can read anyone else's.
Third shape in the atproto permissioned-data series: a Pokémon Go club with its own DID. Ordinary Bluesky posts in a members-only space, moderation notes and labels inside the same boundary, and one allowlisted app view as the only window in.
Permissioned Data Shapes: Community-Moderated Content
ngerakines.leaflet.pubFourth shape in the atproto permissioned-data series: forums. The Gem City Forum mixes public and private categories, moderates with wrapper records instead of labels, and stays open to any app view its members trust.
Permissioned Data Shapes: Forums
ngerakines.leaflet.pub