Comment by digiown
21 hours ago
Assuming it actually works (which I'm not sure about), it increases the cost on the business putting up the ad (presumably targeting you). It acts as a small punishment to the business buying the ads I guess.
21 hours ago
Assuming it actually works (which I'm not sure about), it increases the cost on the business putting up the ad (presumably targeting you). It acts as a small punishment to the business buying the ads I guess.
It also pollutes the data collection on you by advertisers. If you're seemingly interested in EVERYTHING they have no clue about you.
I mean, you're also telling them almost every site you visit. That's strictly worse from a privacy perspective than blocking ads outright.
https://direct.mit.edu/books/book/3112/ObfuscationA-User-s-G...
>Assuming it actually works (which I'm not sure about),
Which it probably doesn't, given that it uses XHRs to "click" on ads, which is super detectable, and given the proliferation of ad fraud I'd assume all networks already filter out.
Google wouldn't have gone out of their way to block it on Chrome if it didn't work.
The other assumption here is that ad networks want to filter out all clicks but the most legitimate.
I don't think that's a very lucid assessment of how advertisers operate on the Internet. We all agree that they could take these steps. If AdNauseam doesn't look like outright fraud in the logs (which they don't if it's all distinct IPs and browsers), I don't think they want to cut it out from their revenue and viewer analytics.
>If AdNauseam doesn't look like outright fraud in the logs (which they don't if it's all distinct IPs and browsers)
You think ad networks don't have logs more sophisticated than default nginx/apache logs? XHRs are trivially detectable by headers alone.