I've just come to realize how important it is for me to run an ad blocker at work. First of all I don't like opening a web site and then start looking for the real content amongst the blinking ad banners. I just don't. And it seems to me that norwegian web sites are the worst. Try visiting www.dinside.no without safety goggles and you'll se what I mean. That site is plain awfull sometimes. www.digi.no has som much ads that they don't even have room for a main article image.
Anyways
We've had some problems with ad blockers blocking items on our web site, so today I've spent some time figuring out how they work. Turns out, there's nothing magical about them. They simply block content based on script naming. Consider these two scripts:
createNew.asp?id=1671
vs
createNew.asp?id=1671&adName=myName
I load them both into an iframe after the page first has been rendered, but one of them is stopped. The last one actually gets blocked because of the querystring variable adName.
Solution
Choose your names wisely. Our system actually is for making ads, so names containing ad*** seemed quite natural at one time. The guys over at Sitepoint has some articles on this topic and this one is worth a read:
http://blogs.sitepoint.com/2009/05/27/file-naming-important/
No comments:
Post a Comment