Imagine all the times you’ve downloaded a one-off app for a conference where you made all valuable connections with colleagues only to never use the app again. We could integrate the conference experience into your professional networks on the Atmosphere. ATproto can make networking so much better.

share atproto architecture diagrams you've seen in the wild

My take on the "explaining atproto" discourse is that all the UX/filesystem/etc metaphors are still very verbose and that you can explain the same idea in a lot less words: It separates data from apps, so any app can use data from any other app. That fits in a tweet, with other sentences around it.

The future of atproto lies in bespoke AppViews: highly tailored features that seamlessly integrate with and elevate existing network-wide behaviors. Due to that, I am incredibly energized by the strategic innovations emerging from SkyBeMoreBlue and BlueSky Radio.

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

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 atproto as a post-app paradigm

Imagining atproto as a post-app protocol starts with materializing the social filesystem – decomposing apps and their data into materials and instruments. For the time being, this guestbook is a good example where the display element is a material and the sign element is an instrument.