Collection
Open
Private & Permissioned Data
ATProto Private & Permissioned data
Collection
ATProto Private & Permissioned data
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 Shapes: Notifications - Nick's Blog
A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.
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).
proposals/0016-permissioned-data/README.md at main · bluesky-social/proposals
Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.
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: 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.
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: 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.
Permissioned Data Shapes: Private Events - Nick's Blog
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.
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 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 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 Interlude: Spaces - Daniel's Leaflets
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.
AT-Communities #1: the Concierge, the Vault, and the Fuck-ass Astro Website – Essential Randomness
In which I try to make sense of communities on ATproto.
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.
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
