does anyone use the email scope for their atproto app? can scopes be made to be optional for users? should I just have users input their email after authenticating for if they want email updates and notifications?
OAuth - AT Protocol
atproto.comMay 17, 2026 at 3:44 AM
OAuth Improvements - AT Protocol
We've been making improvements to the end-user and developer experiences with atproto OAuth.
Building OAuth Authentication for ATProto apps: Part 1, the web use-case - Building on atproto
In this follow-up OAuth implementation guide I dive a bit deeper into the actual implementation details of building authentication for your web or mobile app that builds on top of ATProto.
OAuth for ATProto Apps Part 2: Mobile Implementation - Lost in Inference
Part 2 of a 2-part series on implementing OAuth authentication for ATProto (Bluesky) applications.
atproto oauth2 vs. createSession, scope problems: (transition:generic vs. com.atproto.access) · bluesky-social atproto · Discussion #3211
Summary: When I authenticate via oauth2 on iPhone (via the blueSky page sheet that springs up ), I get an access token with "atproto transition:generic" scope. But passing that token to u...
How do we talk about atproto to non-developers?
The beauty of AT Protocol is that all of your data from different apps is available on your PDS, your own folder on the internet containing your stuff as JSON. This means that you can switch which app you use to view that data, without losing anything. It also makes it very easy to make connections between data stored using different lexicons, or just display activity in one place. Sifa does a nice job of this on your profile page. For web developers, and people who understand webhosting, the concept is reasonably easy to understand. I know that any atproto app I join is going to store data in my PDS, any other people will be able to see it.
if atproto adds E2EE messaging support, will be a bunch of questions: would it be integrated directly in client apps (like Bluesky), or be a separate client app experience? would you have per-app chats (for content sharing), or account-level (generic msgs w/ DIDs)? if the later, why not just Germ?
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgThis is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
