There is a very good question about how @standard.site resonates but the shared @lexicon.community event lexicon doesn’t as much. Would love feedback in this forum thread.
Boris
Yeah I don’t totally understand why “just share a community lexicon” is not resonating for people. Can folks in this thread give feedback? discourse.atprotocol.community/t/shared-lexicons-messaging/6…
Mar 19, 2026 at 3:46 PM
Standard.site - One schema. Every platform.
Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Standard.site - One schema. Every platform.
Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Lexicon Community
Future home of the community known as <a href="https://discourse.lexicon.community">https://discourse.lexicon.community</a>
Lexicon Community
Lexicon Community is a shared space for general discussion of lexicons, lexicon design, and shared usage of lexicons.
Standard.site and Why Coordination Matters More Than You Think - Ewan’s Blog
Interoperability! …and more?
Standard.site and Why Coordination Matters More Than You Think - Ewan’s Blog
Interoperability! …and more?
We wrote a @standard.site explainer — what it is & why it's useful 📝✨ ~shared standards for longform publishing? ~a way to see what friends read & write? ~the atmosphere's hottest collab? yes yes & yes! Seeing lots of q's after Bluesky's new standard.site link card integration. Here's a TL;DR!
What is Standard Site, and why is it useful?
lab.leaflet.pubMy brief blog post on how to publish a lexicon and manually publish a @standard.site post is now the most popular post on my devblog fightwithtools.dev/posts/projects/aramzsxyz/day-…
XYZ Site - Day 21 - Publish another Lexicon and Update a Markdown Post in ATProto
fightwithtools.devYeah I don’t totally understand why “just share a community lexicon” is not resonating for people. Can folks in this thread give feedback? discourse.atprotocol.community/t/shared-lexicons-messaging/6…
Experimenting with the idea of a fully skeuomorphic @lexicon.community events client that focuses on flyers & posters instead of thumbnails/icons and will be aimed at local groups and venues. Just had fun with procedural-generation of the corkboard background.
I think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>
rich harris
atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935
Th relationship between domains and lexicons seems like a short-term win, but it remains unclear for me if it’s good in the long-term.
atproto.brussels 🇧🇪
Loosely related question I have about lexicons being tied to a domain. Domains are not free. So, say your lexicon becomes the industry standard and thousands use it across many apps. It seems fragile to me that the domain belongs to an individual and not a public entity. Is there a solution to that?
Do we have a standard poll lexicon? Feel like I saw a @lexicon.community one floated?
