3 ms·

The adblockers still work on Chrome though. Pretty sure people are figuring out to switch to uBlock Origin Lite and ads -- including on YouTube -- are still be

• TingPing 2y ago
  For now. Advertisers now know ways to bypass all blockers for Chrome.
• unicornporn 2y ago
  They "work", but not well. https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
• zelphirkalt 2y ago
  Until those things don't work any longer. Slowly the frog is boiled here.
  • culi 2y ago
    They will continue to "work". Both v2 and v3 allows extensions to block elements from the DOM. However, only in v2 can they modify actual network calls. With v3, those network calls will still be made. Which means you are no longer protected from tracking and your web browsing experience is once again being slowed down by the loading of ads even if you don't see those ads
    • crazygringo 2y ago
      As I replied to your other comments, this is false. v3 block the network calls. They are not made. You are protected from tracking and nothing is slowed.
• culi 2y ago
  They can still block elements from appearing on your browser but in the background the network calls are still being made. That means you are no longer being protected from tracking and your internet is once again being slowed down by the loading of ads
  • crazygringo 2y ago
    That's not true. The requests themselves are blocked: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest https://developer.chrome.com/docs/extensions/reference/api/d...
    • culi 2y ago
      Lol yeah with a max number of rules being 50 https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/MAX_NUMBER_OF_STATIC_RULESETS https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web... But declarativeNetRequest is the alternative to the webRequest API which Chrome is removing. Using declarativeNetRequest means you have to rely on static rules instead of the dynamic logic that the webRequest API allowed. This is extremely trivial to bypass. So much so that it's basically nothing at all. Especially when you take into account the max ruleset sizes Also in Chrome (and Chrome only) any images or iframes blocked are simply collapsed
      • arccy 2y ago
        330k, not 50 https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-asked-questions-(FAQ)#is-the-limit-on-maximum-number-of-dnr-rules-an-issue https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
      • crazygringo 2y ago
        I try to assume good intentions, but at this point you seem to be simply trying to spread misinformation, and I don't know why. The maximum number of rule sets is 50, not rules, as your own link clearly and unambiguously states. The actual minimum (not maximum) number of supported rules is 30,000: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/GUARANTEED_MINIMUM_STATIC_RULES https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web... In reality, Chrome supports over 10x that. And UBOL doesn't even use/need the minimum, sticking to around 17,000.
• grayhatter 2y ago
  Right, google knows not to turn up the temp too fast, else the frog might jump out!