the point of atproto is to make locked-open apps. apps which are constrained such that they cannot be e.g. bought by billionaires and ruined. yes, doing non-atproto things "enables app developers to do more". yes, non-atproto is "more intuitive" and "it sucks" when you hit atproto's limits.

Every lexicon, every "app" on ATProto is a "yes and" waiting for your contribution to the vision. We're all first party developers.

some thoughts on atproto as a post-app paradigm

the open ecosystem for atproto makes it super easy for one developer to build a compelling and feature rich application in their free time that cannot possibly be maintained by one developer in their free time

been working on something else on atproto this week 🃏

Hot take but I think it’s problematic for atproto that lots of developers i see talking about making stuff focus mostly on things absolutely no end user gives a shit about to fuel their protocols and architecture fetish, and it’s a failure there isn’t another app with like 100k+ users active even.

Looking at all the tech burnout chat today and realizing that I think getting involved in ATProto has really saved my career. The future is bleak but having something hopeful about it in ATProto and the promise of the open web is keeping me going and excited.

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

Some thoughts on why ATProto is so exciting from the perspective of what it could unlock software dev wise.

There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.

difficult to imagine atproto apps building to significant revenue in a world where you can just clone any given app in an afternoon & still access the backing data

difficult to imagine atproto apps building to significant revenue in a world where you can just clone any given app in an afternoon & still access the backing data