Does the idea of "personal context lexicons" have any legs? me.context.timezone → "Europe/Madrid" me.context.perferedLocale → "en-GB" They could be managed on your PDS, and apps could read them as defaults (and store overrides in their own lexicons) Not "profile" information; base context.
Apr 4, 2026 at 3:53 PM
Taxonomy for ATmospheric Lexicon and App Directories
Hi Folks, Dorian again. You may remember me from such poasts as the one a few weeks ago about the protocol-agnostic PDS I plan to cook up. Well I’m back as I’ve been summoned by Christian to tease you all with another one: I know there’s been recent chatter about creating an app directory (or several?), so what might that look like? Even better: what if the metadata that drove such an app directory was on the protocol—so anybody who wanted to make their own app directory could make one? What if...
A folksonomy of lexicons - Chris's Corner
On the design and intent of different lexicons
Context Engineering | Meetup
"Context engineering is the delicate art and science of filling the context window with just the right information for the next step" - Andrej KarpathyLearn about tools, frameworks, and code that is in service of context engineering from practitioners in this space.Dive into the set of strategies fo
ATProto Has a Profile Problem. Lexicon Generics Could Help.
As the Atmosphere grows beyond Bluesky, assuming every user has a Bluesky profile won't hold up. A base profile sounds like the fix, but the UX gets weird fast. Lexicon generics — a pattern built from existing ATProto concepts — could make profile-type records discoverable and translatable across apps without flattening them into a single record.
ATProto Standards Bodies | Sam Clemente | Offprint
How do we go about maintaining lexicons across apps?
Lexicon Store - ATProto Lexicon Schema Registry
Discover and explore AT Protocol lexicon schemas. The verified registry for Bluesky and ATProto lexicons.
Experience Localization: What Non-English Communities Actually Need from ATProto - Nightflight
A specification request from the second-largest language community on Bluesky
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?
✅ community.lexicon.app.defs ✅ community.lexicon.app.entry ✅ community.lexicon.app.profile ✅ community.lexicon.app.profileLocalization
community.lexicon.app.profile Documentation (EN)
lexicon.garden
