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...
First thoughts on integrating with standard.site
Notes on the limitations and unresolved design questions encountered while integrating a blog with standard.site.
Standard.site - One schema. Every platform.
Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Standard.site - One schema. Every platform.
Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
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
We wrote a @standard.site explainer — what it is & why it's useful 📝✨ ~shared standards for longform publishing? ~a way to see what friends read & write? ~the atmosphere's hottest collab? yes yes & yes! Seeing lots of q's after Bluesky's new standard.site link card integration. Here's a TL;DR!
What is Standard Site, and why is it useful?
lab.leaflet.pubWhat 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）
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.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">
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.comatproto/@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.comI 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.devI found a really great article around web standards "Every feature begins life as a non-standard proposal, often shipped. This is not a bug" that I shared with @blaine.bsky.social last September. Thread in the forum discourse.atprotocol.community/t/web-standards-and-the-fall-…
Web Standards and the Fall of the House of Iamus (Alex Russell)
discourse.atprotocol.community
Blaine
I need to write more about this, but one of the core benefits of atproto is that it (dramatically) lowers the cost of coordination, both in divergence and convergence.
