This is a B-sides post with unpolished thoughts that didn’t make it into the main article.
Permissioned data is a love triangle - Nick's Blog
Permissioned data is a love triangle between the user, the identities they grant permissions to, and the applications everyone uses to view controlled data. We don't need to change or reinvent the protocol to have it, because ATProtocol already supports it.
greensky: what does permissioned data feel like? - building [at] habitat
At @habitat.network, we're working hard to launch something at ATmosphereConf. We're building a platform for user data agency: giving users full and transpar…
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.
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 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 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 3: Your Bucket, My Data - Daniel's Leaflets
The third in a series of posts building up a solution to permissioned data on atproto. We look at two different models for where buckets live and why the simpler-looking one doesn’t work out.
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
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).
The Arbiter - Group Management for Permissioned Spaces and Beyond - Zicklag's Leaflets
The permissioned data proposal has the concept of membership, but leaves it to the app to orchestrate it. The arbiter is our idea for a general-purpose, interoperable ATProto group membership service.
[Proposal] Shared private Data for social posting
seconding a sidecar private PDS endpoint attached to the DID document as a good approach in the general case (in an implementation of private data I did which never saw the light of day, this was the approach I took), though obviously it imposes additional constraints on a first mover building this out.
Personal data storage is an idea whose time has come
Data Ownership as a conversation changes when data resides primarily with people-governed institutions rather than corporations.
Private data: developing a rubric for success - Paul's Leaflets
What will an effective solution look like?
The Permission Machine
When Elon Musk calls to imprison the government, it turns out not to matter very much. But when thousands of accounts repeat each other, it matters enormously.
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.