I think that filter file format (and adblocks) should support selective cookie blocking.
There is a huge antiadblock movement in our country and it's successful because of this missing cookie blocking feature. It works this way:
1. Javascript in the website tries to detect an adblocking addon via series of class/id tests and adserver pings at first visit.
2. If adblock is detected, cookie is set with very long expiration.
3. Subsequent http requests are sent with this cookie and server (knowing it's serving to an adblock user) responds with cleverly scrambled html with random classes/ids and with special ads embedded directly inside html with pseudorandom local image urls etc.
That first test is one weak spot but they can change it as quickly as we can change our antidetection whitelists and with every lost battle, eternal cookie is set to all our filter users.
Once this cookie is on, it's almost impossible to target ads in that mess. So it's essential to cancel that one specific cookie. Or at least force them to rename it with every filter update. Nowadays filter updates can't fight ads effectively when they can't delete that cookie.
Example of adblock-immune website:
Code: Select all
http://www.zive.cz/
I suppose syntax should be something like
Code: Select all
||zive.cz$cookie=adb
Thank you for consideration.