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.netFeb 7, 2026 at 6:54 PM
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...
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...
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.
Playing with Parlances - Permissioned Data & AT Protocol - AT-WayFinding
Community privacy is one of our top priorities at @transrights.northsky.social which isn't possible out of the box with any ATproto implementation today that doesn't just hide an entire PDS. We're developing in the open and so I've published a proposal on it, feedback as always is we
What It Means for Universities to Run Their Own PDS: The Potential of DID as Academic Infrastructure - Nightflight
Fragmented Identity Researchers' identities are fragmented. Grant IDs, ORCID, institutional email addresses, ResearchGate, Google Scholar, and various socia…
Federated Identity Community Group
The purpose of the Federated Identity Community Group is to provide a forum focused on incubating web features that will both support federated identity and prevent untransparent, uncontrollable tracking of users across the web. While the community group will take privacy concerns into consideration, these concerns will be balanced against the need to explore innovative ideas around federated authentication on the web.
Adversarial ATProto PDS Migration | Blog
An ATProto account lives on a Personal Data Server (PDS), and that service needs to be hosted somewhere by someone. There are a lot of options here, like a Raspberry Pi in your closet, a rented VPS in a datacentre, or a batteries-included service like bsky.social.
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.
🦫 alert! We published the second episode of "Teach the Web new Tricks", featuring native support for @atproto.com ! Learn more how we improve user agency and privacy at webbeef.org/atproto.html : - Native at:// protocol support. - Log in your PDS and forget OAuth ! - Authorize 3rd parties
Who is writing this idea up? I think we’re going to need it. There are a lot of objects out there being created as regular database entries or associated with the PDS of person who first entered them, but ideally we want to allow the creator or publisher to claim them and redirect without recreating
Paul Rohr
Ah, you're brute forcing this without asking @bnewbold.net + @dholms.at for the AT equivalent of an HTTP 301 or 308 response Mad respect
We're very pumped to announce that the reference PDS now has an account management page! atproto.com/blog/pds-account-management You can now manage permissions, update your password, or deactivate your account directly from your PDS, as a regular user — no command line tools or Bluesky interfaces required!
The Reference PDS Gets an Account Management Page
atproto.com
