I 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
Jun 16, 2026 at 4:45 PM
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.
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...
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://...")
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）
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
I couldn't resist adding support for @standard.site to my blog, and wrote an article about it: j4nk.dev/2026-09-24/atmosphere
Publishing to the Atmosphere
j4nk.devHey #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">
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
at:// link in svelte:head gives error in pre-render mode · Issue #15935 · sveltejs/kit
github.comIf 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.pub👀 @techdirt.com is now posting @standard.site compliant articles... Next up... backfilling our 80k+ article archives. But, for now, every new post should be using the @standard.site lexicon...
Techdirt
The UK’s New Under-16 Social Media Ban Will Cause More Harm Than It Prevents Recently, politicians in the UK pushed forward with plans to eviscerate privacy and free speech on the... techdirt.com/2026/07/13/the-uks-new-under-…
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.comat:// links not opening in Firefox? Now they do ☄️ I made a tiny extension that redirects @atproto.com URIs to your preferred AppView — starting with @bsky.app @blackskyweb.xyz and @bluenotes.social 🩷 Works with posts, feeds, lists, starter packs and both @standard.site publication and documents 🔥
cuducos.me/at-url
tangled.orgatproto/@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
at:// link in svelte:head gives error in pre-render mode · Issue #15935 · sveltejs/kit
github.com
