←back to thread

Bypassing Google's big anti-adblock update

(0x44.xyz)
1034 points deryilz | 4 comments | 12 Jul 25 19:06 UTC | HN request time: 0.001s | source
Show context
crazygringo ◴[12 Jul 25 20:49 UTC] No.44545043[source]▶
> Adblockers basically need webRequestBlocking to function properly. Pretty convenient (cough cough) for a company that makes most of its revenue from ads to be removing that.

Why does this keep getting repeated? It's not true.

Anyone can use uBlock Origin Lite with Chrome, and manifest v3. It doesn't just work fine, it works great. I can't tell any difference from the old uBlock Origin in terms of blocking, but it's faster because now all the filtering is being done in C++ rather than JavaScript. Works on YouTube and everything.

I know there are some limits in place now with the max number of rules, but the limits seem to be plenty so far.

replies(4): >>44545065 #>>44546649 #>>44546946 #>>44550708 #
consumer451 ◴[13 Jul 25 01:13 UTC] No.44546649[source]▶
I believe that another change is that ad blockers cannot update as quickly now? If that is true, since ad blocking is a cat and mouse game, doesn't that make ad blocking with a delay less functional?
replies(1): >>44547023 #
charcircuit ◴[13 Jul 25 02:35 UTC] No.44547023[source]▶
No, that's not true either. Updating rules is allowed. The restriction is about updating code.
replies(1): >>44547063 #
consumer451 ◴[13 Jul 25 02:41 UTC] No.44547063[source]▶
Hmmm, according to this post [0], ad blocking lists must now be updated via store updates. Is that not the case?

[0] https://old.reddit.com/r/uBlockOrigin/comments/17as8o8/the_r...

replies(1): >>44547393 #
1. charcircuit ◴[13 Jul 25 04:04 UTC] No.44547393[source]▶
>Remotely hosted code, or RHC, is what the Chrome Web Store calls anything that is executed by the browser that is loaded from someplace other than the extension's own files. Things like JavaScript and WASM. It does not include data or things like JSON or CSS.

https://developer.chrome.com/docs/extensions/develop/migrate...

Rules are not javascript or wasm.

replies(1): >>44550199 #
2. maxloh ◴[13 Jul 25 13:10 UTC] No.44550199[source]▶
If I recalled it correctly, Chrome's developers imposed a stricter limit on dynamically loaded (fetched) DNR rules. That's why updating rules with the store is the more conventional method.
replies(1): >>44551016 #
3. charcircuit ◴[13 Jul 25 15:16 UTC] No.44551016[source]▶
Chrome allows for 300,000 static rules, 30,000 dynamic rules, and 5,000 session rules.

While not 1 to 1, for reference, EasyList has a little over 30,000 rules.

replies(1): >>44564737 #
4. strbean ◴[14 Jul 25 20:14 UTC] No.44564737{3}[source]▶
Countdown to every ad provider registering 300,001 new domains...