







I read this comment & this post from @jesseplusplus.com and they got me thinking. What if we could make our boring auth even more boring-er? Basically, I don’t think the members list is actually necessary to have on protocol. In the same way we can kick write access up to the application layer, I think we can kick “enumerating readers” up to the application layer. A space host still needs to know who has access to a given space so they can decide whether to mint a credential to a requesting us...
Import members from one list into another, existing list
Link to source code. I'm not logging anything on this server, at least not on purpose, but you should still probably use an App Password then delete it when you're done.
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: OAuth Scopes · bluesky-social atproto · Discussion #3655
Note: a more complete proposal was published in July 2025: https://github.com/bluesky-social/proposals/tree/main/0011-auth-scopes We’re continuing work on rolling OAuth out to the atproto network. ...
Updated Auth Scopes Proposal · bluesky-social atproto · Discussion #4013
This is a discussion thread for the July 2025 Auth Scopes proposal

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.
Crafting a Better Atmospheric Auth Flow
Crafting a Better Atmospheric Auth Flow For the sake of your users ! By @brookie.blog
Crafting a Better Atmospheric Auth Flow
Crafting a Better Atmospheric Auth Flow For the sake of your users ! By @brookie.blog
OAuth for AT Protocol | Bluesky
We are very happy to release the initial specification of OAuth for AT Protocol! This is expected to be the primary authentication and authorization system between atproto client apps and PDS instances going forward, replacing the current flow using App Passwords and createSession over time.


At @roomy.space we've been cooking up the design for the next, ATProto-native iteration of Roomy, and that includes private data on protocol! The first component that we're working on is a group membership service that we're calling the "arbiter". Here's full overview of the design so far!
The Arbiter - Group Management for Permissioned Spaces and Beyond
zicklag.leaflet.pubwhat if we made boring auth even more boring-er? if you're following along on permissioned data, give this a read & let me know your thoughts: discourse.atprotocol.community/t/removing-the-member-list/89…
Removing the member list?
discourse.atprotocol.communityalright protocol devs, some wonky bits: we revisited the recent service auth JWT harmonization proposal, and have a revision up that sticks with a single string 'aud' field. also touches on issuer 'kid', and makes 'lxm' mandatory for XRPC endpoints.
proposals/0014-service-auth-revised at main · bluesky-social/proposals
github.com