Post

rich harris
@rich-harris.dev

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/se..., because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit...

github.comat:// link in svelte:head gives error in pre-render mode · Issue #15935 · sveltejs/kitDescribe the bug I'm adding a link tag using svelte:head like this <svelte:head> <link rel="site.standard.publication" href="at://did:plc:dl64qutkgnbktz6o6ssjn7es/site.standard.publication/3mn3gcyl...
rich harris
@rich-harris.dev

one idea (though it's really only working around the 'DIDs aren't hostnames' issue) would be to use <meta> tags instead of <link>. that's how non-standard-but-widely-understood things like OG images are done, after all feels like the sort of thing to fix now, before problems become widespread

4 reposts42 likes

jared
@awarm.space

hmm, yeah I think the meta tag is a good fit. Just need to think about how to document the change. There's probably a small enough set of consumers that we can get it done pretty quick.

𝕮
@chrisshank.com

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）

jared
@awarm.space

I think we're coming to consensus that it's a good idea yeah! The biggest criticism against imo is that the chance of collisions when you have multiple publications under a single repository is pretty real, and rkey's just avoid that entirely.

Gus
@gu5.org

that drawback makes sense as someone working on tooling though, it's nice to see it coming along (woo!)