3 ms·
solution 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 no
by nikcub 15y ago
solution 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.