3 ms·
>https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnauseam-click-ads https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnause... >AdNauseam 'clicks' A
by gruez 3y ago
>https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnauseam-click-ads https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnause...
>AdNauseam 'clicks' Ads by issuing an HTTP request to the URL to which they lead. In current versions the is done via an XMLHttpRequest (or AJAX request) issued in a background process. This lightweight request signals a 'click' on the server responsible for the Ad, but does so without opening any additional windows or pages on your computer. Further it allows AdNauseam to safely receive and discard the resulting response data, rather than executing it in the browser, thus preventing a range of potential security problems (ransomware, rogue Javascript or Flash code, XSS-attacks, etc.) caused by malfunctioning or malicious Ads. Although it is completely safe, AdNauseam's clicking behaviour can be de-activated in the settings panel.
Isn't this easily detectable? XHRs are easily detectable through various headers, so it's trivial to filter out the fake traffic from this with a few lines of code. I'd expect any ad network worth their salt to implement this. Failing that, thanks to ad fraud there's a whole industry of bot/ad fraud detection firms using browser fingerprinting and behavioral analysis to detect fake ad clicks. I have no doubt that an extension that's "clicking" on every ad using XHR is going to get detected and filtered. I'm very skeptical using this extension will ever achieve its policy goals of fighting against adtech or whatever. You might as well attach a "DNT: 1" header to all your requests.
- stephenr 3y ago> XHRs are easily detectable through various headers Are they though? The most common one (X-Requested-With) isn't inherent to XHR, it's added by js libraries by convention.
- gruez 3y agohttps://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Mode https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Se... https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-User https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Se...
- stephenr 3y agoHuh, interesting. Thanks for the reference.
- tempestn 3y agoI'm not sure what headers you're referring to, but it would be easy for a browser extension to open urls Ina way that would be indistinguishable from a user click. That said, it should be fairly straightforward for ad networks to detect large numbers of clicks from a given device and treat it as bot traffic.
- gruez 3y ago>it would be easy for a browser extension to open urls Ina way that would be indistinguishable from a user click. If they actually opened the page as a tab and rendered it, it would be pretty convincing. However, they specifically decided only to send one XHR request, which is easy to detect because a bunch of behaviors associated with normal browsing (eg. loading css fonts, javascript) doesn't get executed.
- tempestn 3y agoYes, the way they've decided to do it, it would be easy to detect. But nothing would stop an extension from loading the initial page, loading any resources from it, etc., without displaying it to the user. (Not that many people would want to run such an extension, since it would slow their browsing for no benefit.)