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

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

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

also, I kinda feel like calling the things that consume atproto data "apps" does a disservice to understanding what they are / how they work / what their potential is. But that is a partially-formed hot take I can't fully defend yet.

I've been thinking a lot lately about how lexicon authors could help app developers understand intent. #atproto trezy.codes/blog/what-if-lexicons-knew-ho…

More of y’all building ATProto apps need to familiarize yourselves with WCAG

For anyone building new apps and tools on ATproto that are … 🌐 on the Open Web 🌱 past the prototype stage ✨ reimagining the social internet New_ Public, @publicspaces.net and @waag.org are investing up to €10,000 in alternatives to Big Tech Learn more, share, or apply by May 1st newpublic.org/OSA

Plea to #ATproto developers & companies: Pleasepleaseplease make it easier for the rest of us to help boost your apps & tools by creating good, clear documentation geared toward non-techie users? (not just fellow developers or internal team).🤞🏽 See my post on @leaflet.pub.