ATLogin - OIDC for ATProto/Bluesky
ATLogin lets you use your ATProto/Bluesky identity to log in to any application that supports OIDC.
ATLogin - OIDC for ATProto/Bluesky
ATLogin lets you use your ATProto/Bluesky identity to log in to any application that supports OIDC.
Registering Identity Recovery Keys via PDS, using goat | bryan newbold
One of the big design goals for atproto is for users to "own their network identity". If something goes wrong with a hosting provider, it should be possible recover accounts by independently updating their identity to point at a new home. Every account in the network has both a handle and a DID. Th...
Who Actually Owns Your ATProto Identity? Hint: It's Probably Not You
ATProto gives your PDS operator full control of your signing and rotation keys, letting them impersonate you across every app in the ecosystem or kill
com.atproto.repo.createRecord | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
I feel like the logical endpoint is ISPs giving you an atproto identity when you sign up, if you don’t already have one. Would that make things easier? Would we be okay with that, assuming nothing breaks and you can change your PDS afterward?
Ariel M. (she/her)
Changing your phone provider = changing your atmosphere provider → keep your phone number = keep your identity (username) Changing your phone = changing what app you use* → keep your contacts & photos = keep your followers, following, posts, etc. You can change providers without changing phones.
Sep 18, 2026 at 4:38 PM
this is kinda another reason im starting to think more and more that there would be worth in splitting atprotos identity layer out as its own spec and standard. building up handles and oauth around a DID makes for a really flexible cross platform (and potentially cross ecosystem) identity system
Nelind
i kinda hate how atproto adopting DIDs has made people intrinsically associate DIDs with atproto ... it makes some people see me as some annoying bitch trying to shove atproto into places it obviously doesnt belong in when i suggest using DIDs as user identifiers for other systems
Shower thought idea: What about expanding the role of the PDS for account management? E.g. when signing up on atproto with any app/service for the first time, redirect to the already existing account interface (`/account/`) already present on reference PDS, making this flow mandatory to support.
the single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews
Authenticated Transfer Enables Orchestration - nekomimi
blog.nekomimi.petYesterday we launched a new feature and now our existing web users can bring their own DID or we can be a temporary custodian of a new identity. Either way, now every user's PDS is the source of truth for public events and rsvps. openmeet.net/your-identity-your-events #ATprotocol
Your Identity, Your Events: How OpenMeet Gives Every User an AT Protocol Account
openmeet.netI think there might be a need for a javascript library that implements the atproto repo minus the DID authentication and minus the PDS. Use case: being able to start a local-first app offline and cold without login and start creating records, then saturate with identity to sign+sync when online.
