I have pretty strict DNS filtering across the home network, so I assumed it was that. But it still loads for me in Brave on Linux. It didn’t load in Vanadium on GrapheneOS.
In-browser ad bkockers may use anti-anti-ad-blocker filtering rules.
I am pretty sure uBlockOrigin does this by default. But I can’t be sure about the rest at the moment, although my guess is, even the other ad blockers will likely allow at least optionally to set up a filter to remove anti-ad-blocking code from your private copy of a web page you’ve loaded from the net.
DNS filtering naturally will still load all the anti-ad-blocking code, because DNS filtering does not analyze the contents of your private copy of the web page in question.
I am of the opinion that you should NOT have to know all this before you can have a decent and safe experience on the net. It’s shame.
I have pretty strict DNS filtering across the home network, so I assumed it was that. But it still loads for me in Brave on Linux. It didn’t load in Vanadium on GrapheneOS.
Mildly informed speculatuon:
In-browser ad bkockers may use anti-anti-ad-blocker filtering rules.
I am pretty sure uBlockOrigin does this by default. But I can’t be sure about the rest at the moment, although my guess is, even the other ad blockers will likely allow at least optionally to set up a filter to remove anti-ad-blocking code from your private copy of a web page you’ve loaded from the net.
DNS filtering naturally will still load all the anti-ad-blocking code, because DNS filtering does not analyze the contents of your private copy of the web page in question.
I am of the opinion that you should NOT have to know all this before you can have a decent and safe experience on the net. It’s shame.
That seems plausible, and it would make sense of an otherwise puzzling situation.