some thoughts on atproto as a post-app paradigm

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.

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.

I love that the design of atproto was in part inspired by big social Kafka and ScyllaDB server backends and @martin.kleppmann.com's Designing Data-Intensive Applications and the community immediately used it to implement thousands of apps with no backend lol

while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

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

Can everyone building on atproto please answer this question? 😇