while i've been loudly proclaiming in the atproto devs discord meetings that you probably don't need an appview for your atproto side project, i'm now also working on my own "atproto backend in a bottle" that runs on cloudflare workers 😅 still super WIP, but happy for any early feedback

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

It seems a fork lies ahead, is atproto a portable database for a bunch of apps or a new type of post-app, social filesystem?

one thing I really like about atproto is that it provides the infrastructure needed to make open source user apps that actually fucking sync data across devices sorry but the average random hobbyist is absolutely not going to run a user account server for their homebrew todo list app

one interesting future challenge with atproto to me is that you can deploy an atmosphere app and its kind of 0 maintenance if the underlying network doesnt change dramatically, your marginal costs become 0. which means users have no real reason to pay you unless you keep adding stuff?

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.

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