permissioned data

Bluesky permission sets require inconsistent aud parameter · Issue #4850 · bluesky-social/atproto

Describe the bug In trying to rewrite sill.social to use granular permission sets, I've found that app.bsky.authViewAll does not allow access to app.bsky.feed.getFeedGenerator, app.bsky.graph.g...

Getting Started | Stratos

Private permissioned data layer for ATprotocol

Evaluating permissioned spaces for community contexts - meri's missives

A look at Bluesky's proposed approach to private data on ATProto

Owning group data - meri's missives

Thinking about how communities can manage shared data on and off 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.

calendar pt. 1: ATProtocol beyond AppViews - building [at] habitat

our approach to permissioned data (part 1!)

Representing groups in ATProto

I wanted to add book clubs to my GoodReads-like app (Collective), but ATProto doesn't have a standard way to handle shared group resources yet. So I'm building opensocial.community—a separate service that manages groups independently from any single app. This means the same book club could potentially work across multiple apps (imagine your book club having both a reading list in Collective AND a discussion forum in another app), and groups can migrate between providers if needed. It's probably over-engineered for my use case, but might help other ATProto developers building community features.

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.

Early Permission Sets · bluesky-social atproto · Discussion #4437

Progress is coming along on "Permission Sets", as part of the atproto OAuth and permission system. As with other parts of the protocol, seeing how this functionality gets implemented for ...

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.

atproto made simple: granular permissions - underreacted

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.

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.

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.

contrail/docs/05-spaces.md at main · flo-bit/contrail

atproto backend in a bottle. Contribute to flo-bit/contrail development by creating an account on GitHub.