One thing I hope to see after this is more than just the reference implementation of it. An Atmosphere Account ecosystem where PDS providers compete on UX, features, and extensions can be a whole new brand of competition in the open social web, and everyone should lean into it.

Introducing the Micro.blog PDS: manton.org/2026/08/11/introducing-the-mi…

we're gonna see so many "PDS as a media server" apps

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.

One thing I've been toying with, instead of talking about "PDS" and cryptic nonsense like that is: Atmosphere Service Provider, like an ISP but for the social internet. Part of the motivation is that "Sign in with Atmosphere" only works if people have seen that before.

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?

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.