some thoughts on atproto as a post-app paradigm

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

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

some thoughts on atproto as a post-app paradigm

The pitch to community leaders and creators is still taking shape, but the interesting part is the fact that ATProto changes the relationships and power dynamics they and their community have around control of data, vendor lock in, and the flexibility to create new experiences.

Frankly atproto is a great technology that just has yet to really be successfully productized. A few orgs are putting real work into that productization now but only time will tell if it succeeds.

Playing with the idea of ATProto as a marketplace for compute github.com/publicdomainrelay/compute-con…

Lexidraw proves it. Atproto does not exist to build something unprecedented out of nothing: it exists to fuse well-known open-source projects into atproto. The key is the data storage layer. Atproto will latch onto anything, like a remora.

Can everyone building on atproto please answer this question? 😇

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.

Some of us in the ActivityPub world feel jealous of AtProto’s success (like me). But more decentralization is a win for everyone. With Bridgy from @anew.social connecting protocols, this isn’t competition, it’s momentum. We’re stronger together, so let’s build the social web humanity deserves 🚀

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