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

This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.

some thoughts on atproto as a post-app paradigm

I'm going to be launching something pretty big next week, which just happens to include a new atproto AppView, labeler, blob proxy, lexicons. It will have tens of thousands of users, most of whom won't even know they're using atproto, or have even heard of it.

Some initial atproto-related learnings from #Rebuild Helsinki 🇫🇮 * most people building apps here have no idea what atproto is, which is a shame since especially when building social apps, atproto is a great starting point for many reasons

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.

some thoughts on atproto as a post-app paradigm