Earlier quoted context omitted.
It needs to happen in-browser because of the modern prevalence of SSL. I think only Firefox has APIs powerful enough to intercept stuff on this level, and even those APIs are obsolete, so I think it really needs to be integrated straight into a browser fork. Chrome / Firefox WebExtensions have request interception, but I'm not sure it's powerful enough to do this kind of stuff (Also, the mere fact such a scheme would…
The cache/proxy just needs to install its root certificate into your system store and no changes to the browser would be necessary.
Noiszy – A Chrome plugin that creates meaningless web tracking data
161–165 of 165 posts
Re: Noiszy – A Chrome plugin that creates meaningless web tracking data
#162Earlier quoted context omitted.
The cache/proxy just needs to install its root certificate into your system store and no changes to the browser would be necessary.
It's not sufficient due to certificate pinning, and it also completely short-circuits any browser-based security policies keyed on the certificate or options advertised in the protocol like SPDY. That would be the worst possible outcome, and why any correct solution (i.e doesn't break security or functionality) would be hard to reach
Re: Noiszy – A Chrome plugin that creates meaningless web tracking data
#163That would really screw up things for any location tracking.
Re: Noiszy – A Chrome plugin that creates meaningless web tracking data
#164I don't mean to be a curmudgeon, but why put out this kind of privacy-minded plugin for Chrome, one of the browsers I'd probably least trust to respect my privacy?
If you have specific privacy complaints about Chrome, spill it. Content-free finger pointing like this isn't constructive.
Re: Noiszy – A Chrome plugin that creates meaningless web tracking data
#165Earlier quoted context omitted.
Not quite what you're describing, but the venerable Squid cache can do distributed caching. Something, at least, to play with with your nerdy friends.
It needs to happen in-browser because of the modern prevalence of SSL. I think only Firefox has APIs powerful enough to intercept stuff on this level, and even those APIs are obsolete, so I think it really needs to be integrated straight into a browser fork. Chrome / Firefox WebExtensions have request interception, but I'm not sure it's powerful enough to do this kind of stuff (Also, the mere fact such a scheme would…
Consider that SSL is largely used for connection encryption, though it has the additional side-effect of site authentication.
If you can still validate the site, and rely on a hash of the content to detect changes, then you're starting to get toward a cacheable, secure, autenticated, system.
I need to think more about this.