Couple of issues I'm wondering about...
-
Couple of issues I'm wondering about...
First, wouldn't clicking on everything just make you easier to track?
Second, how much bandwidth would all this use?
-
-
Couple of issues I'm wondering about...
First, wouldn't clicking on everything just make you easier to track?
Second, how much bandwidth would all this use?
Also wouldn't this be directing a ton of money to google? (or I guess any other ad provider)
-
Also wouldn't this be directing a ton of money to google? (or I guess any other ad provider)
No, because it devalues their click through, as no sales will result from those clicks.
It's kinda like printing money, there's more of it, but the overall value hasn't increased.
-
Also wouldn't this be directing a ton of money to google? (or I guess any other ad provider)
The advertisers are paying for the opportunity either way. Clicks cost them more money than just displaying the ad. Useless clicks cost them money for nothing.
-
Couple of issues I'm wondering about...
First, wouldn't clicking on everything just make you easier to track?
Second, how much bandwidth would all this use?
Yeah, I can't find an answer whether the "click" is behind some obfuscation, or if the "click every ad" is the obfuscation step itself by attempting to poison the data. The latter may work but yes, may actually increase tracking. Wish that answer wasn't so hard to find on their site.
-
Couple of issues I'm wondering about...
First, wouldn't clicking on everything just make you easier to track?
Second, how much bandwidth would all this use?
- not in this way
- none
the way it works is sending an HTTP request that registers as a "click" to the advertiser (thus costing them money), but then doesn't actually let the browser download any content and fetch the webpage, basically pi-holes the ad and any attached tracking cookies. Combined with the fact that it does this to every ad, it would basically poison any click tracking.
-
- not in this way
- none
the way it works is sending an HTTP request that registers as a "click" to the advertiser (thus costing them money), but then doesn't actually let the browser download any content and fetch the webpage, basically pi-holes the ad and any attached tracking cookies. Combined with the fact that it does this to every ad, it would basically poison any click tracking.
- none
Ah great
it works [by] sending an HTTP request that registers as a "click" to the advertiser
Uh, wait a minute.
Sending a request also uses bandwidth, you know.
-
- none
Ah great
it works [by] sending an HTTP request that registers as a "click" to the advertiser
Uh, wait a minute.
Sending a request also uses bandwidth, you know.
That HTTP request would also show up in the advertisers web logs with your origin IP address.
-
That HTTP request would also show up in the advertisers web logs with your origin IP address.
so use a VPN? if you're the sort of user using AdNauseam, you're probably also the sort of user who already uses a VPN.
-
- none
Ah great
it works [by] sending an HTTP request that registers as a "click" to the advertiser
Uh, wait a minute.
Sending a request also uses bandwidth, you know.
Okay, fine, not enough to matter. Are you satisfied with that?
-
- none
Ah great
it works [by] sending an HTTP request that registers as a "click" to the advertiser
Uh, wait a minute.
Sending a request also uses bandwidth, you know.
A basic GET request, even with a long querystring, will be negligible even on a 1998 dial-up connection.
-
That HTTP request would also show up in the advertisers web logs with your origin IP address.
I think we're far past caring about a website logging an IP address.
-
Yeah, I can't find an answer whether the "click" is behind some obfuscation, or if the "click every ad" is the obfuscation step itself by attempting to poison the data. The latter may work but yes, may actually increase tracking. Wish that answer wasn't so hard to find on their site.
Did you look at the FAQ?
https://github.com/dhowe/adnauseam/wiki/FAQ#how-does-adnauseam-click-ads
-
That HTTP request would also show up in the advertisers web logs with your origin IP address.
What are they going to do? blacklist me and stop serving me ads?
Oh no
-
Okay, fine, not enough to matter. Are you satisfied with that?
-
Did you look at the FAQ?
https://github.com/dhowe/adnauseam/wiki/FAQ#how-does-adnauseam-click-ads
Thanks, I didn't see this, there was a different embedded FAQ that didn't have the specific Q & A below.
But, if anything, it seems to confirm the ad itself is just legitimately clicked from the user's IP address and hidden from the user, and that there is code execution protection, but not that there is any privacy protection? It's still very ambiguous.
How does AdNauseam "click Ads"?
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.
-
"I have drawn YOU as the soyjack and ME as the chad, therefore you lose the argument"
Are you autistic?
Yeah.
Is that a fucking problem?
-
A basic GET request, even with a long querystring, will be negligible even on a 1998 dial-up connection.
Right, but thousands of them, possibly every day? Could perhaps affect your data consumption on your phone e.g.
ā
ļø
-
"I have drawn YOU as the soyjack and ME as the chad, therefore you lose the argument"
Are you autistic?
lol I know right.
-
Okay, fine, not enough to matter. Are you satisfied with that?
Jesus, you got defensive quick and hard. Sorry I rustled you.
https://lemmy.world/comment/16187642
ā
ļø