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
Neither you nor Google has any right, morally or legally, to tell me what to do with the content that Google willingly served to my personal property (my computer). Once those electrons cross that boundry from <Google's property> to <my property> they lose any and all control (although of course in reality they try their damnedest to retain it).

If Google wants to wholesale block all IPs that cause them a problem with click fraud that's their prerogative, but manipulating the electrons that very safely reside within my own private property and then turning around and continuing to serve me ads is something straight out of a Dickens novel and I shudder to think of what happens after the second chapter.

>>pdeuch+Ga1
Of course you can do anything you want. I'm just telling you the potential repercussions, which include destroying someone else's livelihood. If you are OK with that, fire away. But if everyone did the horrible/harsh things that they are legally entitled to do in this world, we would be in a very bad place.

>>downan+Zd1
If your income stream relies on millions of random internet strangers gracefully letting your code live rent free on their own personal devices then you have nobody to blame but yourself. That is assuming that sending GET requests to a public internet endpoint is a "horrible/harsh" thing to do...