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…
What If Lexicons Knew How to Look? - A Thought Experiment About Display Intents on the Atmosphere
trezy.codes
winter
has anyone thought about the multi repo feed yet or are we still in the era of "this is a <app.bsky.*> viewer" and "this is a <site.standard.*> viewer"
Apr 15, 2026 at 3:09 PM
Lexicon Embeds Overview
ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...
ATProto Standards Bodies | Sam Clemente | Offprint
How do we go about maintaining lexicons across apps?
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
Guidance on Authoring Lexicons
At last weekend's Atmosphere Conference, there were a lot of questions about how author Lexicons. I thought it would be a good idea to share some guidance.
HappyView (@happyview.dev)
Lexicon-driven AppView for ATProto. Open source. Maintained by @trezy.codes. https://github.com/gamesgamesgamesgamesgames/happyview
Artist app diary (1): the general idea - hilke thinks
How could an artist focused app on atproto look like? In the first episode of this 'artist app diary' I sketch some general ideas that I have in mind.
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
related: for a number of use cases on atproto, the challenge has shifted from 'how do i get people to use my app' to 'how do i get people to use my lexicon' this also shifts what prototype apps even are
dame
in my experience there is now room to “vibecode” a prototype, evolve it into a more serious app, and then down the road refactor it into something that is more professional, organized, and sustainable previous AI models couldn’t handle large refactors like this, but they now can with human aide
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.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
