Running a CDN on your domain effectively defeats the purpose of CDN.
Comment on Google Chrome coders really, truly, absolutely ready to cull third-party cookies from 2024
barsoap@lemm.ee 10 months agoAny CDN worth its salt can run on your domain so that’s not an issue. The issue is that no third-party anything is pointless as links will just change from nyt.adnetwork.com to adnetwork.nyt.com. I’d rather not encourage that.
Aux@lemmy.world 10 months ago
LufyCZ@lemmy.dbzer0.com 10 months ago
What about a CDN for JS libraries?
What about YouTube embeds?
What about images from Imgur?
Why should all of this be handled by me, on my domain?
barsoap@lemm.ee 10 months ago
You’d tell cloudflare DNS “yo put your stuff on cloudflare-dns.mydomain.foo”. Embeds should be iframes, that is, different webpages, imgur could do the same though yes it’s overkill. Another option would imgur offering an automated API that would allow cloudflare DNS to tell it “here’s a key, please get ready to serve on imgur.mydomain.foo”.
It can all be handled on your domain without you actually running the backing servers. It’s also insanity.