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 Shapes: Forums - Nick's Blog
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.
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 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.
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 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 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: 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 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.
here 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.pubNext up is private events as I explore the shapes of permissioned-data spaces in atproto.
Permissioned Data Shapes: Private Events
ngerakines.leaflet.pubPrivate & Permissioned Data
ATProto Private & Permissioned data
Habitat & permission spaces for organizations - building [at] habitat
Habitat's road to release: 03 ReBAC on spaces - building [at] habitat
Habitat's road to release: 04 Chalk - building [at] habitat
Habitat's road to release: 05 adopting opensocial - building [at] habitat
Permissioned Spaces Made Pretty — Lexidraw
atproto spaces repo export: feels a bit odd to do a giant index block. seems like this will put a low (and hard) cap on the number of record…
