Layers (v0.5.0) now has a pub.layers.changelog lexicon for targeted semantic versioning of all data and metadata components in the pub.layers namespace. docs.layers.pub/lexicons/changelog We've also documented plans for developing an AppView. docs.layers.pub/appview/ Discussion welcome.
pub.layers.changelog | Layers Documentation
docs.layers.pubMar 3, 2026 at 7:06 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...
Metadata on App Engine
There are various bits of metadata about your project and the current request available to your Web app when running on Google App Engine. Let’s see what they are.
Announcing Changesets v3 | Changesets
A tool to manage versioning and changelogs with a focus on monorepos
AppView API · co/core
Read-only XRPC queries over the co/core AppView index — receipts, jobs, providers, and social graph state.
Xcode 26 Release Notes | Apple Developer Documentation
Update your apps to use new features, and test your apps against API changes.
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...
Alex Russell | Web Components and Model Driven Views | Fronteers 2011
There's a lot of tension between today's markup and the semantics we're trying to express in our apps. HTML5 adds a few new types to help describe common cases, but what about when there's no allegory in markup for what you're building? What we need now is infrastructure, not guilt about being "non-semantic". This talk explores new standards-track work in WebKit that's going to enable say-what-you-mean development in completely new ways.
ATProto Standards Bodies | Sam Clemente | Offprint
How do we go about maintaining lexicons across apps?
Layers is a set of ATProto lexicons for representing and interlinking linguistic data across modalities. We're hoping to get feedback on a draft proposal for the lexicons. docs.layers.pub github.com/layers-pub/layers
GitHub - layers-pub/layers: Composable ATProto lexicons for linguistic annotation
github.comMy vision for @skyreader.app and the modern reading app ecosystem. skyreader-dev.leaflet.pub/3mufsapgbec2q
Skyreader Vision
skyreader-dev.leaflet.pubStandard Reader now ships an open AppView for standard.site. Public ATProto queries over the indexed network — publications, articles, feeds, URL resolution. Same lexicons the app uses. Docs + live examples: standard-reader.app/docs/api
API · Standard Reader
standard-reader.appLexicon suggestions for reader apps on AT Proto (such as @leaflet.pub Reader and @skyreader.app): - storing the reading status of a given URL - “liking” or “recommending” an URL - public (and when permissioned data will be out, private, or access controlled) folders to organize subscriptions
There are a lot of architectural bits, but if I had to pick one design feature it's Lexicons. Lexicons allow for new shared data types and structures in a way that are immediately available on network for any other service provider to adopt. Getting shared agreement in ActivityPub is hard.
Pedro Vezza
Why did you decide to bet on atproto over Mastodon or similar?
