Tag: spaces
Habitat's road to release: 03 ReBAC on spaces
Fine-grained permissioning on top of spaces.
@dholms.at was right
In which I admit I'm wrong, on the internet
Habitat's road to release: 02 sap for syncing permissioned spaces
A package to help apps keep permissioned data up-to-date.
Permissioned Data: Space Access
Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
Permissioned Data Shapes: Notifications
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 Shapes: Feeds
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: Polls
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: Forums
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
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
A private events space is the first shape with other people in it: a member list of friends and family, guest RSVPs that live on the guests' own PDSes, and an app allowlist that controls which services ever see the venue address.
Permissioned Data Shapes: Self-Only Bookmarks
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 7: Off the Record
In which we put records in a repo, sign them, and sync them (but not quite the way you think).
Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does
AT Protocol is public by default. Everything you write goes into a signed, archived, and rebroadcastable repository that anyone can read from and moves through relays. This core design decision makes the network so legible and easy to build on, but it also blocks entire types of apps, like private groups, gated content, member-only forums, or anything that isn’t meant for everyone.
Habitat & permission spaces for organizations
Our plans for organizational permissions on spaces
Permissioned Data Diary 5: What’s in a Name?
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
A special edition of the data diary that sketches out the rough shape of where we're heading.
Permissioned Data Interlude: Spaces
In which I retcon the naming of everything.