3 ms·
I don't think a combo of dns aliasing to the ad network, plus better embedding ads in the dom to make them look like a site's regular content, plus random order
by bsaul 11y ago
I don't think a combo of dns aliasing to the ad network, plus better embedding ads in the dom to make them look like a site's regular content, plus random ordering of news and ads to prevent any kind of static css rules matching can be countered.
Now of course that means ads will require a bit more work to integrate to a website, and probably move integration deeper in the server side, but technicaly i don't see any major issues. Am I missing something ?
- rblatz 11y agoMost ads that pay the highest are retargeting ads. Meaning you went to an online store looked at gadgets, that site included a snippet of js that said to the ad network, "hey he looked at gadgets". Now the ad network shows you ads for gadgets from that site. There isn't a good way to build that deeper into the server, cookies don't work that way.
- bsaul 11y agoYou could configure the js to use another domain name to talk to, ( the same as the original site), that would be just an alias to the ad network. Ad blockers work on the http level, not on the dns one, so there's no way for them to know the redirection did happen. Or you could make it all happen on the server side. Just have the ad network provide a server side plug in that would analyse incoming http request for user blueprinting, and ask the ad server what ad to display. Then you'd just have to include that content in your response.
- deleted 11y ago[deleted]