3 ms·
>the AdNauseam (.io, browser extension) approach to pollute their tracking data might be inspirational. The gist is: can't eliminate ad links? Then have an app
by gruez 4y ago
>the AdNauseam (.io, browser extension) approach to pollute their tracking data might be inspirational. The gist is: can't eliminate ad links? Then have an app "click" all of them randomly so that counters become irrelevant. So there is this link that identifies user X?, well then write an extension that distributes and "clicks" it around on say 1000 other machines in a p2p way so that it becomes meaningless.
Except if you look at the documentation for AdNauseam, their fake click technique seems trivially filterable. The fake clicks are made as XHR requests, so all you have to do is look at the appropriate headers to filter them out. At best the only adtech companies that are getting fooled by this are upstarts that haven't added fraud detection yet.
https://github.com/dhowe/adnauseam/wiki/FAQ#how-does-adnauseam-click-ads https://github.com/dhowe/adnauseam/wiki/FAQ#how-does-adnause...
- Klonoar 4y agoUnless I'm missing something, headers here can also be set to appear as another request type. (And to be clear - I could be missing something. Does the browser allow replacing e.g Sec-* headers on XHR requests?)
- gruez 4y ago>Does the browser allow replacing e.g Sec-* headers on XHR requests? Probably not, according to this snippet from MDN > With this information a server can implement a resource isolation policy, allowing external sites to request only those resources that are intended for sharing, and that are used appropriately. This approach can help mitigate common cross-site web vulnerabilities such as CSRF, Cross-site Script Inclusion('XSSI'), timing attacks, and cross-origin information leaks. https://developer.mozilla.org/en-US/docs/Glossary/Fetch_metadata_request_header https://developer.mozilla.org/en-US/docs/Glossary/Fetch_meta... being able to override it kills the whole point of the headers.