Permissioned data on vlpds: every member keeps a private, signed space repo on their own PDS. It never reaches the firehose, and reading it takes a short-lived credential chain.
Permissioned Spaces - WG.1
@Permissioned Spaces Expressive Authorization at the PDS @verdverm.com | @blebbit.app
Permissioned Spaces - WG.1
@Permissioned Spaces Expressive Authorization at the PDS @verdverm.com | @blebbit.app
Permissioned Data: Space Access - Nick's Blog
Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
Overview | HappyView
Spaces are containers for permissioned data in atproto. Unlike regular public records that live in a user's repo, space records are gated by membership — only members can read or write data within a space.
Spaces | contrail
Auth-gated store for records that can’t live on public PDSes — private events, invite-only groups, members-only chat. Opt-in; zero cost if you don’t enable it.
Overview · vlpds docs
An atproto PDS whose only durable storage is an object store. Any node serves any request, one node can run a personal server for free, and a few nodes can carry all of Bluesky's write load.
Atproto spaces · aturi.to
Browse your permissioned atproto data: records kept outside your public repo.
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
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 Interlude: Spaces - Daniel's Leaflets
In which I retcon the naming of everything.
@dholms.at thinking about permissiones data. What if: Permissioned data URI was at://<PDS did>/<record type>/<rkey> exactly the same as public data. The PDS would handle the space assignment opaquely and do a 4xx response with some space aturis. Client goes and grabs a space cred and retries
Sixth in the permissioned data series: what spaces do to feeds. The firehose stops at the space boundary, the credential flow becomes your membership source-of-truth, and one feed URI serves a different skeleton to every viewer.
Permissioned Data Shapes: Feeds
ngerakines.leaflet.pubThere is one area with Permissioned Data Spaces that I haven't seen discussed. It reveals that data is currently stored in the (I think I'm coining a term here) *Public Space* on Personal Data Servers. Remember, most people on Bluesky aren't aware of where their data is stored, or what that means.
the simplespace managing-app thing makes it very easy to define space access based on arbitrary info, without managing an actual member list. you could create restricted spaces based on: - handle on a domain or TLD - PLC identity minted in a time window (eg, elders only) - account labels
Spaces explainers
Search terms: AT Protocol Spaces, ATProto Spaces, permissioned data, buckets
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
The Atproto Spaces Alpha is Live - AT Protocol
Reintroducing Spaces - Daniel's Leaflets
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
