Post

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...

15/6/26, 2:22 pm2 reposts67 likes

Mastro.{js,ts}

@mastrojs.bsky.social

15 June

Yeah, that really seems an oversight in the @atproto.com design 😅 Also means you cannot construct AT-URLs with the standard JavaScript URL class (the constructor throws).

rich harris

@rich-harris.dev

15 June

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

jared

@awarm.space

15 June

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

16 June

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

16 June

yeah i think something like this would be super handy!

Mastro.{js,ts}

@mastrojs.bsky.social

15 June

hear, hear! Next up: rkeys of type any ?

jared

@awarm.space

15 June

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.

mATt terenzio

@librenews.bsky.social

15 June

this should be the answer. it's early enough and this allows for extension

Jake Lundberg

@jakelundberg.dev

15 June

i like this idea…reuses existing solutions that everyone is already familiar with. you have my vote, sir!

Tom Sherman

@tom.sherman.is

15 June

DID's not being URI-compatible is a long standing wart of the protocol, it's a much wider issue than just standard.site unfortunately 😞 @bnewbold.net has written a bunch about the trade offs but I'm not sure what the current position is

Tom Sherman

@tom.sherman.is

15 June

I seem to remember both "let's get the URI spec to accommodate DIDs" and "let's change the AT URI spec" positions being thrown around at different times 😅