Questions:

mcc@mastodon.social

Questions:

- What if we added something to HTTP where if you're only fetching a page to read OpenGraph tags, you send a special header saying "I only want the OpenGraph data", and the server then has the option of sending only the <meta> tags and nothing else?

- Could this help with the Mastodon "hug of death" (because the server can generate a simpler version of the page, caches can behave differently etc) where many instances rush to generate preview cards driving the previewed site offline?

trwnh@mastodon.social

@mcc i think ive posted before about an idea for what is basically http HEAD but it also returns html <head>. or otherwise some http headers that fulfill the same use case as opengraph, so the existing http HEAD can return those.

asoftdessert@mastodon.social

@trwnh @mcc Headers would get clunky (especially with H2/H3), and HEAD must return the same as GET, so data would be potentially duplicate. Maybe using Accept with an extended mediatype, which would be cache friendlier?

trwnh@mastodon.social

@asoftdessert @mcc one thing that is funny about content formats is that a lot of them have metadata headers and content bodies, but you can just stuff an entire head+body into another body with its own head, matryoshka style. you can just keep doing this arbitrarily as long as your consumer knows which layers to unwrap and how

anyway for http i think http resources having headers plus the HEAD method can work with zero unwrapping

if you wanna conneg media type perhaps application/oembed+json?

NodeBB-ActivityPub Bridge Test Instance

Questions: