Now that @robin.berjon.com has released an initial spec and implementation of Web Tiles, we can see how we can use or extend this as a base for Lexicon Embeds. Lexicon Embeds is my label for how to have native ATProto content embed in different apps, from display all the way to interactivity— eg an event post in bsky with an RSVP button. Getting this as a general capability - and getting security and display right - means embeds can function in Leaflet and Bsky and anywhere else, rather than o...
Web Tiles as the base for Lexicon Embeds
Now that @robin.berjon.com has released an initial spec and implementation of Web Tiles, we can see how we can use or extend this as a base for Lexicon Embeds. Lexicon Embeds is my label for how to have native ATProto content embed in different apps, from display all the way to interactivity— eg an event post in bsky with an RSVP button. Getting this as a general capability - and getting security and display right - means embeds can function in Leaflet and Bsky and anywhere else, rather than o...
Web Tiles as the base for Lexicon Embeds
Yeah this would be absolutely fantastic. I don’t see yet how the Bsky app would discover which embed to use for a linked record but I assume some sort of definition in the actual record? Anyway, hope to read more about this
Lexicon Embed
How do we embed, display, and render different Lexicons across the ATmosphere?
Web Tiles
Tiles are composable web docs and apps that can safely be used in arbitrary contexts and assembled from multiple sources to carry out complex user interface tasks.
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...
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
Lexicon Embeds Overview
There’s an excellent discussion and thread about syntax highlighting of code blocks happening today: I think most notably there’s some alignment around using a lexicon to represent code blocks (say Tangled’s strings) and embedding those, rather than just doing syntax highlighting w/in the constraints of a bsky post. This seems like a good place to hammer a bunch of things out.
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
This generated some discussion so I want to expand on it a bit The context is that standard.site doesn't currently have any lexicons for the actual content. The idea is that the document content is covered by leaflet, offprint, pckt, or other lexicons. But...
Paul Frazee
You shouldn’t use lexicons that don’t actually exist
Hey @danabra.mov, I’m working on a new labeler for arbitrary atproto records. I’d like lexicon owners to be able to suggest how to render their lexicons in the app. I’m thinking maybe @inlay.at components as sidecars?
Trezy
I'm working on a new labeler software (i.e. an alternative to Ozone) and this really feels like the right way for these things to work. 😎 #atproto
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
