3 ms·
It would stop some tracking, but the people doing the tracking have many clever (and some not so clever as sometimes the simplest things just work!) ways to fin
by dspillett 11y ago
It would stop some tracking, but the people doing the tracking have many clever (and some not so clever as sometimes the simplest things just work!) ways to fingerprint you beyond cookie values. See things like https://en.wikipedia.org/wiki/Evercookie https://en.wikipedia.org/wiki/Evercookie for an example of how much trouble you really need to go to in order to try avoid being tracked.
I keep toying with the idea of writing an add-on that doesn't just destroy tracking cookies (well, any non-white-listed cookies) but instead shares them around randomly - so next time you visit a site you might have the cookie from last time I did, or someone the other side of the world... That would also not affect anyone using mixed techniques like Evercookie (the discrepancy between what each state store has recorded could be seen and used to throw out the data instead if letting it pollute the tracking pool). Of course care would need to be taken here: if you share cookies from sites that take authentication you could open up session hijacking vulnerabilities. Only storing/sharing cookies from HTTP sites might help (no site requiring authentication should be running through un-Sed HTTP) but wouldn't be a perfect solution.
- fnordfnordfnord 11y agoWith the current state of affairs I think that poisoning the well is a better tactic than trying to prevent being tracked.