some thoughts on atproto as a post-app paradigm

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

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

adding social features to our websites will accelerate atproto adoption faster than building pure atproto apps

I made an atproto dashboard to see what's going on on the network in realtime. Runs entirely in your browser. Take a look. What would you like to see? atproto.nrempel.com

Tried to explain a bit of the use case of @varsityapex.com and why it made sense to integrate ATproto features. A full fledged site would make even more use, for the demo just opted to make records of non-score items. Tour: varsityapex.com/tour Was fun to explore the problem space a bit

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.

@danabra.mov do you think it makes sense to frame atproto as providing a data and identity layer to the web, or as aiming to improve the web? I never want to overstep (see crypto claiming web3) but atproto is extremely web-brained like you said, and the web is where a lot of the utility shines

Found a conventional use for atproto (replacing high school state associations/athletic conference/school sports websites) the other day and built a spec because I couldn't help myself. it's live but I'll share a blog post about it before sharing