Mapping web pages to canonical AT records
I’d like to use this thread to riff on a community practice of mapping web pages to their canonical AT record. This is something that standard.site already does as a way to verify publications and their documents using <link> tags. Unfortunately Rich Harris pointed out that this isn’t technically valid, so there is discussion for a breaking change for standard site to use the <meta> tag. Making this work with any lexicon/record has quite important ramifications for the entire ecosystem (I’m writ...
Mapping web pages to canonical AT records
I’d like to use this thread to riff on a community practice of mapping web pages to their canonical AT record. This is something that standard.site already does as a way to verify publications and their documents using <link> tags. Unfortunately Rich Harris pointed out that this isn’t technically valid, so there is discussion for a breaking change for standard site to use the <meta> tag. Making this work with any lexicon/record has quite important ramifications for the entire ecosystem (I’m writ...
URL Fragment Text Directives
Copyright © 2023 the Contributors to the URL Fragment Text Directives Specification, published by the Web Platform Incubator Community Group under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available.
URL Fragment Text Directives
Copyright © 2023 the Contributors to the URL Fragment Text Directives Specification, published by the Web Platform Incubator Community Group under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available.
Declare and resolve website links for at:// URIs. A demo of the me.byjp.atproto.deeplink lexicons.
The AT-URI Syntax Mess - at:// pizza thoughts
Why AT URIs are not valid under IETF RFC-3986, what the impact is, and some possible ways forward.
Marque · Your name, on the open web
Domains for your next idea. Built on the AT Protocol, made for the open web.
What are you’re thoughts on making this breaking change more inclusive to any AT URI? Like for @semble.so it would be very useful to have this mapping or any webpage that has a corresponding AT record (e.g. microblogging, standard.site, steamplace videos）
Jun 16, 2026 at 4:38 PM
If you're an #atprotodev I'd love your thoughts on this short proposal. I think we'd all benefit from a way to tag our HTML to reference the at:// uris they're derived from! @popfeed.social, @bookhive.buzz, @sifa.id, @leaflet.pub, @pckt.blog, @offprint.app and many more — penny for your thoughts?
Atproto markup for HTML
byjp.leaflet.pubnew data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)
Permissioned Data Diary 5: What’s in a Name?
dholms.leaflet.pubHey #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">
Seriously mild take: ATProto web clients should serve a <link rel="alternate"> containing an at:// URI I've just opened a PR to do this on Frontpage and atproto-browser. I'd for other clients to follow along with the convention! github.com/likeandscribe/frontpage/pull/…
Add AT URIs as alternate links by tom-sherman · Pull Request #172 · likeandscribe/frontpage
github.comI think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>
rich harris
atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935
this is also a thing, but separate from the basic website stuff anna is talking about. the at:// potential is sort of about navigating to that sort of URI in browser bar. but I think more realistically, having anchor links. <a atref="at://..."> (or more realistically: data-atp="at://...")
Working with @standard.site more, I'm getting a better understanding of it's intentions and uses. An interesting thought: If you define your site's structure and content on your PDS, you can actually change the web addresses, including domains, of the content.
