3 ms·
> There's a handful of scripts that are linked on a large portion of web sites. This means we can expect these resources to be in cache, right? Not any more: Si
by sneak 6y ago
> There's a handful of scripts that are linked on a large portion of web sites. This means we can expect these resources to be in cache, right? Not any more: Since Chrome 86, resources requested from different domains will not share a cache. Firefox is planning to implement the same. Safari has been splitting its cache like this for years.
[most of the top common resources are Google (and FB) ad tracking]
I read this as Google is willing to spend millions upon millions to move huge amounts of additional unnecessary network traffic to make sure only they can reliably track most people across the whole of the web.
- minitoar 6y agoGotta spend money to make money
- ivanbakel 6y agoEven if Google didn't have a stake in targeted advertising, shared caches lead to easy identification - browsers have a duty to close off any avenue by which users can be tracked.
- damagednoob 6y agoI don't use any externally hosted scripts on sites I develop. Security is part of the reason but the bigger problem I find is tying uptime to somebody else whom I have no control over.