We should be able to make this work by spinning up a server that proxies content from https://sveltejs.github.io/assets but adds COEP/COOP/CORP/whatever headers. Not 100% sure if it'll work for range requests (i.e. the video), but it'd work for images, and should be simple to implement using edge functions

https://learn.svelte.dev/tutorial/sharing-code now works! Will try the video example next. Not sure what to do about the other two examples (and the https://httpstatusdogs.com example I wanted to add for error pages) since proxying other people's stuff is a bit cheeky

Proxying everything sounds risky, but if we scope that to to a whitelist of what we have in the tutorial (the video link, status dogs, the link to those image placeholders), it would be ok?

it'd be scoped, yeah. i'm not too concerned about risks, i'm more concerned about ethics/legality. hotlinking is one thing, but proxying is another

Man, I can't figure out how to get range requests to work. https://learn-svelte-dev-git-range-requests-svelte.vercel.app/assets/media/caminandes-llamigos.jpg works fine, https://learn-svelte-dev-git-range-requests-svelte.vercel.app/assets/media/caminandes-llamigos.mp4 barfs (though if I remove the range and if-range headers, it works fine, you just have to buffer the entire thing before you can watch any of it)

Going to leave it for now, there are more pressing matters to deal with

closing this as audio elements work fine, and we're no longer using video