Since I don’t have time to dig into this yet, question: if I build a service that relies on this (say, @squire.quest) what happens to users with a PDS that doesn’t support this implantation yet. What’s the planned experience?
dad (aka miguel)
oh shit, offprints about to pop off atproto.com/blog/atproto-spaces-alpha
Aug 21, 2026 at 10:02 PM
What is required to make a PDS implementation?
This Github thread from July 2024 had a long answer by Bryan Newbold that is included below:
Proposal: OAuth-based account creation · bluesky-social atproto · Discussion #4587
We recently added to the reference PDS (and underlying OAuth Provider) implementation support for Initiating User Registration via OpenID Connect 1.0, however, what I wasn't aware of when I add...
Protobase
Managed AT Protocol PDS infrastructure for your brand. Give your users a home on the Atmosphere — we handle the heavy lifting.
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...
The Reference PDS Gets an Account Management Page - AT Protocol
Announcing the addition of an account management interface to the reference PDS
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.
Yesterday 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.netIt's true — fetching authenticated data directly from a PDS is a pain in the butt. And it's totally worth it.
Making Websites is More Complicated These Days - And That's a Good Thing
alexanderson.leaflet.pubOk, this will sound a little crazy, but if I'm managing my keys, what would happen if I turned my browser into my PDS? Like, I only use my PDS when im logged in, everything else gets mirrored by relays ... What would happen if my PDS was running locally as my browser?
Sam Goto
I made a decision on this: I'm going to keep using did:plc. There are many technical pros/cons, but I'm going to take a bet on people and use this product as the people designing it are using it too. Here is to changing ones mind!
I think we need a "PDS as a Service". There are a bunch of little apps I'd love to make, but I don't want to have to host a PDS for each of them for anyone who doesn't already have an account. But I'd be fine with allowing them to register to a PDS with my app's domain and pay a fee per sign up.
I’ve said this elsewhere but I would KILL for (and pay for) a service to host my PDS and have an AP server running off that same data, the way Fedisky set out to enable one social web source of truth. micro.blog feels uniquely positioned to provide this, any chance you’d consider doing that?
GitHub - msonnb/fedisky: ActivityPub extension for Bluesky PDS
github.comOk, this will sound a little crazy, but if I'm managing my keys, what would happen if I turned my browser into my PDS? Like, I only use my PDS when im logged in, everything else gets mirrored by relays ... What would happen if my PDS was running locally as my browser?
Sam Goto
I made a decision on this: I'm going to keep using did:plc. There are many technical pros/cons, but I'm going to take a bet on people and use this product as the people designing it are using it too. Here is to changing ones mind!
