One does not simply "detect adblock". Browsers are user agents. They run code in an environment optimized for user safety and convenience. These environments will always be able to tell your site's server- and client-side code exactly what it wants to hear while showing something different to the user. You can't stop it. The client will always win.
We may eventually get to the point where clients use various computer vision techniques to recognize ads. If I can clearly distinguish jiggling, improbably large elf anatomy below a flashing yellow "PLAY THIS ONLINE RPG" from content I want to see, so can an algorithm, at least to within an acceptable error rate.
Advertisements that are so borderline that they can't be detected as advertisements are ones I probably don't mind seeing anyway.
Spammers have already tried all available countermeasures and they've completely lost. Spam is so completely ineffective that it's actually dipped below half of email traffic.
No, the client will always win in the end.
The techniques used by the project to which you've linked can be trivially worked around by detecting the script itself and either not running it or telling it what it wants to hear. (Come on: an iframe? You really don't think a browser extension could lie about that? I expected at least some kind of server-client traffic correlation for a serious ad-blocker-blocker attempt.)
That is unfortunately not the case in all situations now (e.g. mobile devices).
Now guess if I block ads?
The only reason the client can separate certain forms of advertising from content is that advertisers - by and large - don't care. The more advertising and content is intermingled the more difficult it will be to separate them. The intermingling is already happening as we see in the rise of content marketing.
Maybe lightbox you from time to time asking for the same.