What if an advertiser agreed with a website to point the DNS of the website to a server which the advertiser controls, who then serves a page which uses javascript to load the actual website off a subdomain and in the process injecting advertising which is coming directly from the server the advertiser controls, i.e. the original domain of the website
Can current adblocking methods block this?
What if an advertiser proxies the entire website?
>load the actual website off a subdomain
So just visit the "actual website" and not the domain that injects the ads?
>>62150532
This would probably break all hosts-file based or DNS based adblockers.
It wouldn't work on browser extensions though, which targets the javascript elements and stops them directly.
What's the best anti-anti-adblock?
>>62150532
This is already done via server-side ad injection. Blocking is done on cosmetic filters. It is an arms race for sure.
>>62150668
The advertiser could control the DNS as well and generate a random subdomain name which expires every few hours
>>62150683
>>62150723
The "loader" could use some shit like shadow dom to make the elements impossible to detect via cosmetic filtering
>>62150839
Adblockers would just start to use statistical models. Only real way to combat this is native advertising, though FTC rules limit this a bit.
>>62151012
If ad blockers have to do heavy statistical calculations to block ads then wouldnt it really slow down loading times?
>>62151058
Can share this cross browsers. And most of the calcs are gonna be straightforward.
>>62150532
donT use GUI
>>62150532
adblocking is immoral. THE END