this is kinda another reason im starting to think more and more that there would be worth in splitting atprotos identity layer out as its own spec and standard. building up handles and oauth around a DID makes for a really flexible cross platform (and potentially cross ecosystem) identity system

Another OIDC gateway approach for using your atproto account to login to many different things tangled.org/bkb.arcnode.xyz/atauth Nice work @bkb.arcnode.xyz!

Once you experience shared lexicons and the benefits of a single portable identity, it feels like a new open network. But the most important part is that it practically works as an extension of the web. We can add social features to our websites without even mentioning atproto. Frictionless adoption

If WSocial sold people on the idea that everyone they would interact with is ID-verified, then indeed, every single open ATProto community would act as a back door of sorts. The only way for them to deliver would be to de-federate entirely. And it's always a bad idea to bet against openness.

its actually really cool that instead of having my own account system i can now just integrate atproto oauth into whatever project i'm making and instantly have everything i need in terms of user identity

I built a translator between Atproto's OAuth and OIDC, so apps like @tailscale.com can use your Bluesky identity. It includes a whitelist so you can invite people directly using their DID!

i think it's time someone made a google suite alternative in atproto, have that be the "default" PDS; literally just replace sign in with google then everyone understands the concept of oauth and we can move on with our happy atmospheric lives

🧵 I've been wracking my brain around ATProto onboarding. Why do all ATProto apps make you create a new account before you can do anything interesting? Why don't we let people start with an email address or phone #? Then claim your identity if/when the need actually arises.