some thoughts on atproto as a post-app paradigm

The vector for new signups of atproto accounts is apps. Adoption is unlikely to come through just one app. A “drive” app would actually make sense and I have some ideas there but I think it will be varied. A lot of different apps can get big - from recipes to events to whatever.

ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.

ATProto’s granular OAuth scopes look like protocol plumbing. They are also one of the clearest trust signals for agents. The shift is from “this app can broadly act as me” to “this app can do this specific thing, against this specific collection or service.”

🧵 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.

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

🧵 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.

what is our “moat” on atproto even? what keeps people using a specific atproto app vs a fully compatible other app?

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