Michael Morris
First Post
Yesterday I let my temper lash out and I hinted that adblock countermeasures may be used to stop adblock programs. I want to clarify some things about those statements and hopefully put some of the outcry to rest.
First off, while this should go without saying, no change to the code or site is made without Russ' explicit approval. While Russ hasn't commented on my tirade yesterday you can rest assured that if he's opposed to it then it will never come to be.
With that out of the way, I'm going to try to explain what the big deal is about ad blocking anyway.
ENWorld's total page views are it's 'inventory' of possible exposures. In a typical month this is around 8 million. Ads are sold through two means - Click thru and exposure. We only use exposures - so our only obligation to the advertiser is to actually show the ad. If the ad fails to entice a click that's not our problem.
Ads are sold in 1000 unit lots. The cost to ENWorld of ads being blocked by a single user is insignificant. However be mindful of the old truism - "No single raindrop believes it is responsible for the storm."
When many users block the advertisements it adds up after awhile. Colloquial estimates are that perhaps 8-10% of users block ads. I would guess that ENWorld is slightly higher because more of the users here are technically astute enough to look into ad blockers and implement them.
Ten percent of 8 million is still 800,000 "lost" pages. I call them lost because there is no way to recoup the cost of sending those pages. However, the pages remaining should be able to run enough ads to make up for the loss.
The problems truly start as that percentage increases. If the inventory drops below a certain point we are rendered unable to raise enough money to pay for the bandwidth the site consumes. When that happens ENWorld closes it's doors.
No - it is not in danger of happening.
Adblock countermeasures use a variety of means to detect and defeat adblockers. The simplest measures are to avoid labeling the image size in the HTML or the css, not using id and style tags containing "ad" at the start or end and the like. Having the ad image delivered from the same machine also helps a great deal and defeats a majority of the adblockers out there since the blocker can't tell if the ad is a legitimate image or not.
More invasive than this would be using javascript to inspect the dom on page load complete. Ad blockers work by stopping the loading of the image tag - so if the tag never completes loading the javascript can be instructed to do some form of behavior in reaction. One possibility is to nag the user about the adblocker.
More invasive still is to set the page css to display: none and then toggle this property back to display: block once the ads are confirmed to have loaded. Browsers won't display the content in this case - google spiders are unaffected because they ignore css anyway. Defeating this is possible, but beyond the time most people are willing to spend.
For what it's worth before any such plan would go into effect I'd need proof that it would be effective and worth time to create and maintain the block code. As long as the block rate is lower than around 10% not including google spiders I really could care less. However if it's crosses over 40% or more then yes, I will consult with Russ and with his permission install countermeasures. We know the page serve rates and can compare them to the ad serve rates.
Will that drive people off the site? Damn straight it will - but such with such users gone the bandwidth usage will decrease and the hosting rates will drop. I'd rather not see costs offset that way, but given the choice of seeing the site go down because it can't be funded any longer I'll settle with being a villain and driving off users who don't want to view ads by force.
If there was another revenue stream available I'd use it. I hate the ads too for what it's worth and they annoy me everybit as much as they annoy everyone else. As an added bonus I had to spend 2 hours of my time installing the code for them that I would have rather spent doing **anything** else. But until such a stream is discovered and implemented (I am working on one possibility) or someone with a couple million dollars around to put into a trust to permanently fund the site shows up there will be ads.
First off, while this should go without saying, no change to the code or site is made without Russ' explicit approval. While Russ hasn't commented on my tirade yesterday you can rest assured that if he's opposed to it then it will never come to be.
With that out of the way, I'm going to try to explain what the big deal is about ad blocking anyway.
ENWorld's total page views are it's 'inventory' of possible exposures. In a typical month this is around 8 million. Ads are sold through two means - Click thru and exposure. We only use exposures - so our only obligation to the advertiser is to actually show the ad. If the ad fails to entice a click that's not our problem.
Ads are sold in 1000 unit lots. The cost to ENWorld of ads being blocked by a single user is insignificant. However be mindful of the old truism - "No single raindrop believes it is responsible for the storm."
When many users block the advertisements it adds up after awhile. Colloquial estimates are that perhaps 8-10% of users block ads. I would guess that ENWorld is slightly higher because more of the users here are technically astute enough to look into ad blockers and implement them.
Ten percent of 8 million is still 800,000 "lost" pages. I call them lost because there is no way to recoup the cost of sending those pages. However, the pages remaining should be able to run enough ads to make up for the loss.
The problems truly start as that percentage increases. If the inventory drops below a certain point we are rendered unable to raise enough money to pay for the bandwidth the site consumes. When that happens ENWorld closes it's doors.
No - it is not in danger of happening.
Adblock countermeasures use a variety of means to detect and defeat adblockers. The simplest measures are to avoid labeling the image size in the HTML or the css, not using id and style tags containing "ad" at the start or end and the like. Having the ad image delivered from the same machine also helps a great deal and defeats a majority of the adblockers out there since the blocker can't tell if the ad is a legitimate image or not.
More invasive than this would be using javascript to inspect the dom on page load complete. Ad blockers work by stopping the loading of the image tag - so if the tag never completes loading the javascript can be instructed to do some form of behavior in reaction. One possibility is to nag the user about the adblocker.
More invasive still is to set the page css to display: none and then toggle this property back to display: block once the ads are confirmed to have loaded. Browsers won't display the content in this case - google spiders are unaffected because they ignore css anyway. Defeating this is possible, but beyond the time most people are willing to spend.
For what it's worth before any such plan would go into effect I'd need proof that it would be effective and worth time to create and maintain the block code. As long as the block rate is lower than around 10% not including google spiders I really could care less. However if it's crosses over 40% or more then yes, I will consult with Russ and with his permission install countermeasures. We know the page serve rates and can compare them to the ad serve rates.
Will that drive people off the site? Damn straight it will - but such with such users gone the bandwidth usage will decrease and the hosting rates will drop. I'd rather not see costs offset that way, but given the choice of seeing the site go down because it can't be funded any longer I'll settle with being a villain and driving off users who don't want to view ads by force.
If there was another revenue stream available I'd use it. I hate the ads too for what it's worth and they annoy me everybit as much as they annoy everyone else. As an added bonus I had to spend 2 hours of my time installing the code for them that I would have rather spent doing **anything** else. But until such a stream is discovered and implemented (I am working on one possibility) or someone with a couple million dollars around to put into a trust to permanently fund the site shows up there will be ads.
Last edited: