zlacker

>>yuvada+(OP)
It's pretty simple: this has to be wreaking havoc with Adsense - depleting ad budgets, artificially inflating CTRs, and giving website owners revenue they didn't earn. This extension also exposes website owners to unfair Adsense bans for generating high numbers of invalid clicks, which can cost them two months of revenue that is almost always withheld when Google bans a site. So by using this you could be costing someone (your favorite blogger etc.) their livelihood.

If you are going to block ads, block them. Don't click on them.

>>downan+Zb
How can the Adsense distinguish whether it is AdNauseum clicking or the human clicking?

>>abhv+9f
They probably can't, since it's an extension and thus uses the user's browser, IP, cookies etc (Adsense does use mouse tracking and other techniques that will likely flag these clicks as suspect, requiring additional analysis). Therein lies the problem. It appears to them as if someone is going and clicking on every ad, or is using an automated headless browser to click on ads. That can easily get you banned. Google doesn't care about who is doing it, they only know that it is happening on your site, and as a result will treat your site as a threat to the Adsense network.

>>downan+Of
How about clicks from browsers that have this plugin installed are just not counted? That sounds simple enough.

>>ryanhu+Nh
They could certainly do that in this case, but they are probably trying to send a strong message to would-be developers of similar extensions. One is a nuissance; a thousand would be much more difficult to chase down and block.

Also, if these developers really wanted to, they could distribute it directly from their site and dynamically generate the extension, packaged with a unique identifier, for each download. This would make it effectively unblockable. So simply identifying an install of this specific extension is not a solution.