3 ms·
Immutable cache and subresource integrity get us most of the way there. I don't know if web browsers share those across domains, but I don't think there's a rea
by scrollaway 7y ago
Immutable cache and subresource integrity get us most of the way there. I don't know if web browsers share those across domains, but I don't think there's a reason not to.
- captncraig 7y agoPossibly privacy. If I host a copy of a popular site's Js, I can watch download patterns and have a pretty reliable "has this user logged into site X" detector.
- johannes1234321 7y agoWhat you could do is the negative "they won't load this file" which could have many reasons (from connection breaking just after the HTML to JS blockers) And I believe it's a good solution to restrict such a feature to files already marked with a hash on the origin. They would only do that for common libraries found elsewhere as well.