It's a valiant effort, but there's really no way they'll win this battle. The client simply has too much control.
I was toying with writing a chrome extension for sites/videos that behave differently when adblock is running. It shouldn't be too hard to make the site believe that the ad content is running, when it's not actually running.
Not a perfect approach, but if bandwidth / compute / memory is not an issue, it could be a novel way to respond to more sophisticated ad block detect mechanisms that come out.
The purpose of our method is to detect the usage of ad blockers for informational purposes. For example, if you have a site that displays ads you'd probably like to know how many of your visitors are blocking them.
You could add a rule to allow ads.js for each site's domain that's using the method as we've described, but a site could easily dynamically cycle through the thousands of file name combinations contained within EasyList.
You're right - it's about sites that display advertising gaining a better understanding of how their revenue is affected by ad blockers. Once they know that they can have an informed discussion on what, if any, changes are needed.
I was toying with writing a chrome extension for sites/videos that behave differently when adblock is running. It shouldn't be too hard to make the site believe that the ad content is running, when it's not actually running.
Not a perfect approach, but if bandwidth / compute / memory is not an issue, it could be a novel way to respond to more sophisticated ad block detect mechanisms that come out.