







new data diary! (and i think final in the main series) this gets into the permissioned repository itself. how it's structured, signed & synced. give it a read & as always, lmk your thoughts!
Permissioned Data Diary 7: Off the Record
dholms.leaflet.pubJul 17, 2026 at 12:30 PM
Permissioned Data Diary 7: Off the Record - Daniel's Leaflets
In which we put records in a repo, sign them, and sync them (but not quite the way you think).
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 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
The first in a series of posts about major design decisions along the way to a permissioned data protocol for atproto.
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.
Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does - Nick's Blog
AT Protocol is public by default. Everything you write goes into a signed, archived, and rebroadcastable repository that anyone can read from and moves throu…
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.
as a little pre-show surprise, here's an early draft of the permissioned data proposal! github.com/bluesky-social/proposals/pull…
Permissioned data by dholms · Pull Request #94 · bluesky-social/proposals
github.comAT Protocol Developers
Don't forget, @dholms.at is joining us for the livestream TOMORROW for a permissioned data AMA.
as a little pre-show surprise, here's an early draft of the permissioned data proposal! github.com/bluesky-social/proposals/pull…
Permissioned data by dholms · Pull Request #94 · bluesky-social/proposals
github.comAT Protocol Developers
Don't forget, @dholms.at is joining us for the livestream TOMORROW for a permissioned data AMA.
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.pubhere it is folks! lots of details to still nail down, but this is roughly where our heads are at for the design of a permissioned data protocol give it a read and let me know your thoughts!
Permissioned Data Diary 4: The Big Picture
dholms.leaflet.pubhere it is folks! lots of details to still nail down, but this is roughly where our heads are at for the design of a permissioned data protocol give it a read and let me know your thoughts!
Permissioned Data Diary 4: The Big Picture
dholms.leaflet.pubMe and @zicklag.dev have been having a closer look at the system sketched out in @dholms.at's Permissioned Data Diaries - we generally like it! And have some scenarios in mind that may be worth considering
Evaluating permissioned spaces for community contexts
meri.leaflet.pub