atjson is a living content format for annotating content
standard.site/lexicons
Shared lexicon schemas for long-form publishing on AT Protocol. Uses typescript to json via prototypey.
Developer docs · atjam
Build on the at.atjam.* lexicons, or extend them for your own domain — tutorials, how-to guides, an extension guide, and the API reference.
human.json
A lightweight protocol for humans to assert authorship of their website content and vouch for the humanity of others.
A beginner's workflow for Lexicons development in AT protocol web apps - We Can Just Do Things
An experimental approach to designing and implementing Lexicons with TypeScript + Next.js
The control layer for AI
The industry spent two years teaching LLMs to speak JSON. That work mattered: free-form text was unusable in production. Today, every serious inference provider uses some implementation (often open-source) of structured output. Structured output has become essential infrastructure that the team at .txt is proud to have spearheaded. Even as the ecosystem evolves, and open-source alternatives emerged, our engine remains the state of the art.
The control layer for AI
The industry spent two years teaching LLMs to speak JSON. That work mattered: free-form text was unusable in production. Today, every serious inference provider uses some implementation (often open-source) of structured output. Structured output has become essential infrastructure that the team at .txt is proud to have spearheaded. Even as the ecosystem evolves, and open-source alternatives emerged, our engine remains the state of the art.
oauth-client-metadata.json | AT Protocol Community Wiki
A community-maintained wiki for the AT Protocol ecosystem
Blogging on the open social web - and more exciting features - pckt - Dev Journal
ATmosphere — referring to the growing ecosystem of applications built on the AT Protocol, a federated protocol for open social platforms. Not to be confused ...
Aturi is a new service that provides universal links for traversing/sharing content in the ATmosphere. Share @bsky.app posts or @atproto.com data with in a way that lets recipients choose where they want to view it — @blackskyweb.xyz, @leaflet.pub, @anisota.net, @pdsls.dev, and more! aturi.to
aturi.to - Universal links for the ATmosphere
aturi.to
Anisota
ATmosphere Waypoints Powered by a new sister service called @aturi.to, navigate to different areas of the ATmosphere automatically like @blackskyweb.xyz, @leaflet.pub, and more. ➳ Jump to clients or apps ➳ Copy links to specific waypoints ➳ Configure default waypoint behavior anisota.net
Hey #atprotodev; should we make a convention for annotating HTML elements with the AT uris they’re built with? (So that, say, a browser extension could offer links to @pds.ls) Something like this? <li typeof="schema:Thing" resource="at://did:web:example.com/org.example.lexicon/rkey">
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...
P(aul) Frazee
You shouldn’t use lexicons that don’t actually exist
Community notes over papers is another example of a new kind of annotation that goes far beyond merely a "mention" and can be easily incorporated into protocol powered research ecosystems like #ATScience
