Resolve AT Lexicons over the network
danabra.mov/resolve-lexicon
Resolve AT Lexicons over the network https://resolve-lexicon.pages.dev/
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
blowdart/idunno.AtProto.Lexicons
A collection of lexicon implementations for AT Protocol for use with idunno.AtProto
Lexicon Store - ATProto Lexicon Schema Registry
Discover and explore AT Protocol lexicon schemas. The verified registry for Bluesky and ATProto lexicons.
An AT Proto lexicon currently under consideration and development
An AT Proto lexicon currently under consideration and development · GitHub
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
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?
