Comment on Google Chrome warns uBlock Origin may soon be disabled

hal_5700X@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

• partial_accumen@lemmy.world ⁨3⁩ ⁨months⁩ ago

  Google an ad company are killing ab blockers Chrome browsers. Yeah, that sounds right.

  FTFY

  source
• timewarp@lemmy.world ⁨3⁩ ⁨months⁩ ago

  MV3 doesn’t kill ad blockers. uBOL (uBlock Origin Lite) blocks ads, is by the same author and uses MV3. The issue is MV2 made it way too easy for malicious browser extensions to do bad things, like read the content of every page you visit. MV3 makes it much harder for malicious browser extensions to do these things, but makes it harder to do things like intercept network requests.

  Some of these “features” that classic uBO used are available in MV3 but requires different permissions. Some of them could also be implemented with native messaging. The main uBO author though feels slighted by Google and went on a trash talking campaign against Google, and to be fair had a few good points. Anyway, most people on social media now care more about how Chromium and Firefox makes them feel now irregardless of facts. They think their emotions somehow are the same as facts.

  source

  • partial_accumen@lemmy.world ⁨3⁩ ⁨months⁩ ago

    The issue is MV2 made it way too easy for malicious browser extensions to do bad things, like read the content of every page you visit. MV3 makes it much harder for malicious browser extensions to do these things, but makes it harder to do things like intercept network requests.

    Then allow a savvy user to choose to keep MV2 mode via an opt-in control instead of depreciating years of hard work by non-malicious extension authors. uBlock Origin is, in fact, the ONLY browser extension I use in Chrome, as Firefox is my main browser.

    source

    • timewarp@lemmy.world ⁨3⁩ ⁨months⁩ ago

      I agree they should have tried to find more ways to keep the old behavior. MV3 rollout has already been delayed for a long time, and now users merely get a message. I’m not sure that the community (mostly Google contributors) won’t give in or try to find a way to keep MV2. However, what was done with MV2 can now be done with MV3 with native messaging or other network tools… I think the concern is that allowing an exception makes it much easier for a malicious extension or software to get users to agree not realizing what they’re agreeing to. Furthermore, the declarative approach is actually preferable by many. You get most of the same features without exposing all your traffic to an extension.

      source
  • TrickDacy@lemmy.world ⁨3⁩ ⁨months⁩ ago

    And yet the likelihood of Google publishing a malicious extension is quite low. Not sure why you’re so adamant about defending their shitty anti-adblock actions, making excuses for a mega corporation.

    source
  • Phoenix3875@lemmy.world ⁨3⁩ ⁨months⁩ ago

    From my understanding, MV3 kills vital features of ad-blockers in that

    1. Some filtering rules do rely on the ability to read the content of the webpage, which can’t be migrated, per the FAQ linked in the article
    2. The declarative API means updating the rules means an update to the plugin itself, which might get delayed by the reviewing process, causing the blocker to lag behind the tracker. It might not be able to recover as quickly like in the recent YouTube catch-up round.

    source
  • sapporo@sopuli.xyz ⁨2⁩ ⁨months⁩ ago

    . Some of them could also be implemented with native messaging.

    Some? Or all?

    uBlockOrigin would still loose some of its features and capabilities nonetheless, even if a sub-set of them could be implemented in other ways. Not?

    source