Hello! @snarfed.org and I have been talking about moving typed extensions forward, so we just submitted a lexicon.community PR using proxy links as a first concrete application:
Background
This proposal started from Connecting records, web pages and apps, which raised the issue that at-tags let a web page point at its record, but nothing lets the record point back at the page (or at its copy on Mastodon, or on someone’s personal site, and so on). To verify a page ⇔ record connection, we agreed we needed “something” that:
- tool builders always know where to find
- can link back to the page (and thus validate the relationships)
Enter—
community.lexicon.meta.links
community.lexicon.meta.links provides a shared place to link a record to its web pages, representations on other networks, or other resources identified by a link relation. It takes inspiration from the rel HTML attribute and builds on @snarfed.org proxy links lexicon’s sketch which is based on FEP-fffd (the fediverse convention for canonical and alternate links).
For example, a post that is also published on a website and another network could include:
{
"$type": "app.bsky.feed.post",
"text": "Hello from my website!",
"createdAt": "2026-10-18T12:00:00Z",
"community.lexicon.meta.links": {
"$type": "community.lexicon.meta.links",
"links": [
{
"href": "https://alice.example/posts/hello",
"rel": "canonical",
"mediaType": "text/html"
},
{
"href": "https://social.example/users/alice/statuses/123",
"rel": "alternate",
"mediaType": "application/activity+json"
}
]
}
}
Paired with embedding at-tags in HTML meta tags, a record like this would create bidirectional validation for a URL associated with a record.
Typed Extension
This lexicon double as a “proposal” for typed extensions, a new extension pattern. These are:
- A “standardized” field with a defined meaning (in this case,
"community.lexicon.meta.links") - Namespaced to a specific lexicon
- Whose value is expected to conform to that Lexicon (in this case,
community.lexicon.meta.links)
Here, while it’s possible to create “classic” sidecar records with the community.lexicon.meta.links lexicon, we reccommend people embed this lexicon in other records when possible, as seen above. That means:
- this extra data travels with the record
- people can stumble on it in the wild and find the definition using existing AtProto methods
- there’s no ambiguity in case of
rkeycollision (see Disambiguating sidecar records)
The cost of doing it this way is that one needs to be able to edit the record to add links, and every edit changes the record’s CID. We think it’s fine for this case.
Let us know if you have thoughts!