3 ms·
This could backfire massively if the court says "no problem". Better Privacy and Ghostery plugins are your friends, turn off local storage in about:config -> d
by ck2 15y ago
This could backfire massively if the court says "no problem".
Better Privacy and Ghostery plugins are your friends, turn off local storage in about:config -> dom.storage.enabled
Etags is rather clever though, not sure how to ignore those.
added: also remember to turn off third-party cookies in Firefox (it's there but buried in Chrome)
Note to developers: please never, ever, rely on third-party cookies!
- nikcub 15y agosolution to Etags is to block all third-party requests by default, and let the user selectively allow for each site they use. Working on a plugin to do that now: http://github.com/nikcub/parley http://github.com/nikcub/parley (a bit inactive only because I haven't committed to gh since initial commit, but I will be in the next few days) the last-modified header can also be used to track - it accepts anything. I described it in a comment on the last thread: http://news.ycombinator.com/item?id=2825564 http://news.ycombinator.com/item?id=2825564
- pornel 15y agoBetter solution to Etag and cache-based tracking in general would be to change browser cache from: cache[url] = data to cache[(url,origin)] = data (origin is roughly the domain of the referrer) This way you don't need to block all 3rd party requests and caching will still work reasonably well for each site.
- ordinary 15y agoFor Firefox there's RequestPolicy: https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/ https://addons.mozilla.org/en-US/firefox/addon/requestpolicy... RequestPolicy is an extension that improves the privacy and security of your browsing by giving you control over when cross-site requests are allowed by webpages you visit.