What if everything is just routed through the backend and still is able to track you?
Comment on Google Chrome coders really, truly, absolutely ready to cull third-party cookies from 2024
Pxtl@lemmy.ca 10 months ago
Kill third party everything. No more CDNs, no more tracking pixels, no more cookies, no more content from anything but the domain in the url bar.
derpgon@programming.dev 10 months ago
Black616Angel@feddit.de 10 months ago
But that is a lot harder to do and requires more resources.
If you have a tracking pixel now, the company directly knows your browser from you downloading that pixel. If they were to implement the single-backend stuff, the site would have to gather all that information themselves and then send it to all the trackers. But they can’t just send it somewhere, because then everyone could send bogus info to them so you need verification and an api and that is costly and each company would build their own api so you need to buy a program that speaks all those apis… You get the point. It’s a LOT more work than just pasting the text for some pixel somewhere on your site and let the others do the rest.
Plopp@lemmy.world 10 months ago
Yes please.
Aux@lemmy.world 10 months ago
No more CDNs is a bad fucking idea.
barsoap@lemm.ee 10 months ago
Any 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.
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.
Aux@lemmy.world 10 months ago
Running a CDN on your domain effectively defeats the purpose of CDN.
OrderedChaos@lemmy.world 10 months ago
Why?
ilinamorato@lemmy.world 10 months ago
CDNs like CloudFlare reduce load on smaller servers through caching and delivery of common assets, which reduces load times (helping to democratize sites as it’s not just big companies that can afford quick websites). CDNs also prevent DDoS attacks and can improve uptime.
They’re pretty critical pieces of internet architecture. Not that they’re perfect, but banning all third party content from sites is kind of a baby/bathwater situation.
lemmyingly@lemm.ee 10 months ago
CDNs also reduce load on the network. Why pull a resource from a server on the opposite side of the world when a CDN on my ‘door step’ can provide a cached version of it.
OrderedChaos@lemmy.world 10 months ago
Ah. Thanks!!
Aux@lemmy.world 10 months ago
The purpose of a CDN is to better cache common resources between different web sites. For example, if you’re using a Roboto font from Google CDN on your web site, just like many other web sites do, the user who previously visited other sites with such font will load your web site much faster and will spend less traffic, because he already has this font from CDN in their cache. It also means that you save money on hosting.
If you remove CDN from the equation, you punish yourself and your users. That’s a very dumb idea. Especially when CDNs are free to use.