Post

I'm not sure if it's the most impactful, but I think probably moving the social-app to use OAuth. OAuth is the chosen/recommended path for auth, and it's really solid as is. But I think for atproto apps building in the style of the social-app (XRPC proxying, client holds auth)...

there's still some pain points with the 2 week max auth. I think if Bluesky was dogfooding it, it could help improve that experience, whether it's TMB or client assertion backend since that would probably have to be the path for the social app to use OAuth. Will give better experience to devs who...

0 reposts32 likes

Want to build atproto applications in this manner as well. Added bonus is I think it would help in the long run show a bit more that Bluesky is an application on the Atmosphere, and you are logging into a service provider instead of the Bluesky app, which in turn might help...

people feeling comfortable logging in to an account they already have on other atproto apps if they see a familiar login that they experience when logging into an atproto app they already trust with their password (Bluesky).

I think there is prob more on the front of selling "Sign in with atmosphere" that will be needed. But I think everyone using similar screens will help build that trust and is a great first step towards explaining the idea of "You have one account on the internet that you own"