3 ms·
> CDN is common enough technique which should be standardized in browsers. HTML should include link to resource hosted by site and its checksum. Now browser can
by fenollp 10y ago
> CDN is common enough technique which should be standardized in browsers. HTML should include link to resource hosted by site and its checksum. Now browser can easily use cached resource from any other site with the same checksum or just download it from site.
I really like this idea! Store your heavy assets in a public DHT with each browser storing a part. Then fetch said assets by content-hash if not already in cache.
Maybe disable serving for mobiles.
The W3C needs to get on this!
- willglynn 10y agoThe W3C has a thing called subresource integrity, which is basically what vbezhenar described: https://www.w3.org/TR/SRI/ https://www.w3.org/TR/SRI/ However, there are reasons why e.g. hash-addressed JavaScript are not used as a shared cache: https://hillbrad.github.io/sri-addressable-caching/sri-addressable-caching.html https://hillbrad.github.io/sri-addressable-caching/sri-addre...
- fenollp 10y agoWRT the "timing attack": In most cases, client does not even request bytes from CDN which is then not able to track Client. But then again CDNs can implement tracking based on this lack of requests (which is kind of ironic and should be infeasible the more clients use this technique I think). Actually the other issues are solved by the "DHT" part of this idea: no centralized party can track which assets are already in your history. The only tracking I can think of is by your nearest neighbours's browsers. If such a neighbour N empties your cache (DNS attack?) it will trigger a full fetch from N. Then N can attempt to fingerprint this assets query with what other pages list. But then the whole point of this is to cache assets that are used on most pages! I love this idea. Let's make the Web decentralized again! (I couldn't resist)