Post

I've made another little service that unfurls URLs into nice metadata for a few projects. Naturally, I'm adding @standard.site support but the question is should that take priority over other metadata? E.g. a standard site document overwrites the og:title

7/6/26, 4:28 am1 repost14 likes

Mastro.{js,ts}

@mastrojs.bsky.social

7 June

Probably do what most social apps currently do? i.e. what does the Bluesky app do?

Jim Ray

@jimray.bsky.team

8 June

We ran into this with Leaflet/pckt where they generate a custom `og:image` if you share selected text. I fear the answer is going to be a bit case-by-case, alas.

Willow (GHOST)

@willow.sh

8 June

Oh interesting, did you end up preserving that custom image or use the one for the whole document?

Jim Ray

@jimray.bsky.team

8 June

In that case, we use the custom image, so the og tag overrides the standard site image. Annoyingly case by case!

Kevin Marks

@kevinmarks.com

7 June

Here's a page for you to test: kevinmarks.com/partialsilos

kevinmarks.comFacebook users see part of the truthThey won't be curious enough to find out more.

Willow (GHOST)

@willow.sh

7 June

I'm returning normalised metadata as opposed to the raw things, that way the consumer doesn't have to reimplement the logic just to do something like `standardSite.title ?? og:title ?? title ?? etc`

Willow (GHOST)

@willow.sh

7 June

Still a lot to add, but I must sleep - still, here's the link if anyone wants to play with it or send patches (apologies for the GitHub use, old habits die hard) github.com/ghostdevv/un...

github.comGitHub - ghostdevv/unfurl-worker: A Cloudflare Worker that extracts meta data from URLsA Cloudflare Worker that extracts meta data from URLs - ghostdevv/unfurl-worker