Let us open 100 tabs of pure madness to fool trackers
trackthis.link
trackthis.link
(Links to the blog post about this - https://blog.mozilla.org/firefox/hey-advertisers-track-this/)
IMO, to hide true traffic you'd need to run a constant steam of noise requests, in which the real visits would be undiscernible. And the noise might need to be non-uniform, unpredictable and still follow the patterns of normal traffic, so it can't be filtered out.
Solved.
Thinking it through though there are potentially massive problems, the first of which is that I can think of ways to circumvent it to a large extent with deeper fingerprinting, and if I can no doubt the ad servers could if they the system became popular enough for them to care. Other issues would include making sure useful cookies were not swapped out causing both security and usability issues for the participants.
Or they were designed by people with little knowledge of relevant security matters.
Or little care for security matters: all too often people throw together a proof-of-concept (naively leaving out thought of concerns like that, as they can be addressed in proper development later if the PoC is successful) then find it being rushed into production without the required review/refactor...
And besides, I imagine most people who care enough to use tools like this have personalised ads disabled already
However, if it becomes popular...
¯\_(ツ)_/¯
1: https://help.duckduckgo.com/company/advertising-and-affiliat...
As I mainly use DDG and considering I get a fuck-you hardest-level (or simply "sending too many requests") recaptcha every time I want to use a site that uses it… What difference does it make? For the few cases where DDG's stupid "let's ignore search terms" decision bites me I can simply use startpage with !sp