Cc: @lukemulks
It's only fraud and only costly if you have to deliver the fake clicks to parties you want to benefit. If you just want to burn the whole ecosystem to the ground it's less complex.
-
-
This is not how click fraud is accounted for.
-
Specifically, if you do not work to fake humans well, then current anti-fraud tech used in ad-tech to discount "non-human traffic" has it easy. So you end up having to build stuff on par w/ MethBot, even if you do not defraud publisher revenue shares. And fee-takers still profit.
-
The ad
#blocking issue is solved by returning 0.0.0.0 as#DNS address resolution for any#tracker#adnetwork#socialmediamarketing IP address. This is solved at the router level, by filtering outbound port 53 TCP/UDP packets. Very easily accomplished with@ubnt components. -
Now .. imagine if you could connect to a
#DNS#nameserver that would do this as a "service" working with@Akamai,@Azure,@AWS caching infrastructure <of course>#adblocking solved .. by switching your#DNSresolution IP address .. <voila> -
This is a temporary hack reliant on fundamental privacy bugs in current internet infrastructure that need to be fixed. It's not a viable solution. If done as a service, it entrusts that service with your browsing privacy.
-
name one
#DNS resolver that isn't privy to all this kind of information. ... and let's not even get started on routing (especially via traceroute hops to foreign 'states' ... -
That's why it needs to be fixed, and why your solution can't last.
- 2 more replies
New conversation -
-
-
See my more recent replies.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.