Just wanted to let you know that Adblock Latitude can't bypass BlockAdblock successfully for the time being. It's not the only anti adblock system that ABL can't deal with, but I'm afraid BlockAdblock could be a success in the web if it's not defeated at time.

The "BlockAdblock" site you linked to seems to do some trickery, without using javascript, which places a white "sheet" over the loaded page.

One workaround for this is to remove unwanted page elements, and the tool I recommend for this is "Nuke Anything Enhanced" by Patrick Salloum. Using the addon, you can right click and "Remove this object" two times (once on the "we block here" textbox, and again on the white "sheet"), and see the entire page you linked to.

lyceus wrote:I can confirm that neither the Nuke Anything Enhanced and the rule works on Pale Moon +ABL. The site is blocked after some seconds of view by a layer.

My apologies: the BAB page is viewable if Nuke Anything Enhanced is used to remove the two unwanted top "sheet" layers, and if javascript is disabled. NoScript is one such javascript-control addon which works well with Pale Moon.

Hiding element id "babasbmsgx", you hide the blocking sheet which overlaps the actual page. To find out what element is overlapping others, simply use Pale Moon's Inspector (CTRL SHIFT C) and once you found the culprit element (by hovering the mouse pointer on the web page), click on it (to get the corresponding line selected in the page source window), then look at "id=" or "class=" and choose which to block.

What is missing to AdBlock is the ability to insert wildcards in the id/class name, since some sites will generate them pseudo-randomly to try and evade such blocks...

dinosaur wrote:What is missing to AdBlock is the ability to insert wildcards in the id/class name, since some sites will generate them pseudo-randomly to try and evade such blocks...

The site did in fact regenerate the page-covering elements after each page refresh, each time with a different, random-looking name. At least that's what I saw.

But the four filters posted above (as "Option B") were effective in my profile that uses ABL (with/without Reek AAK) provided they were all used.

KNTRO wrote:Here's a website using BAB — it may be a little slow at its first load, but it might be helpful —or not— to understand how BAB actually works.

This site (that actually uses 'blockadblock' in real life) didn't put up any anti-blocking messages or barriers at all for me, neither with ABL nor uBO.

I'm guessing a blocker's performance on an example/proof-of-concept site such as 'blockadblock.com' might not be a reliable predictor of what will happen when BAB is used by any other site in actual practice.

I should mention that if you are installing Reek's Anti-Adblock Killer (AAK) in Pale Moon, you should install GMforker's Greasemonkey for Pale Moon (experimental) rather than the Greasemonkey that Reek links to, which is for Firefox.

Be not the first by whom the new are tried, nor yet the last to lay the old aside. — Alexander Pope

I'm a happy user of uBlock origin and its element selector. Previous to that, I successfully used AdBlock Lite + Element Hiding Helper for similar problems to this. The rule which allows me to see BAB is: blockadblock.com###hDImVWJHzFlGyvioHZDFOLN8LooCLa . Even though I cleared cookies, etc. and reloaded a couple times, I didn't see the "we block adblock" screen again until I disabled that rule. I don't see anything like that on bild.de, either with or without the rule.