Google’s campaign against ad blockers across its services just got more aggressive. According to a report by PC World, the company has made some alterations to its extension support on Google Chrome.

Google Chrome recently changed its extension support from the Manifest V2 framework to the new Manifest V3 framework. The browser policy changes will impact one of the most popular adblockers (arguably), uBlock Origin.

The transition to the Manifest V3 framework means extensions like uBlock Origin can’t use remotely hosted code. According to Google, it “presents security risks by allowing unreviewed code to be executed in extensions.” The new policy changes will only allow an extension to execute JavaScript as part of its package.

Over 30 million Google Chrome users use uBlock Origin, but the tool will be automatically disabled soon via an update. Google will let users enable the feature via the settings for a limited period before it’s completely scrapped. From this point, users will be forced to switch to another browser or choose another ad blocker.

Archive link

  • vzq@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    3 months ago

    I’ve heard reasonably good reports about ublock origin lite (uBOL), the manifest V3 implementation. I haven’t made the jump yet, though.

      • vzq@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        Maybe. I’m on Firefox, but a lot of my family members are on Chrome and I’m not looking forward to the calls ;)

    • ReversalHatchery@beehaw.org
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      3 months ago

      It may still block a relatively large part of the ads, but uBlock is not just about blocking ads. Large parts of it’s filterlists are about blocking data mining, shitty cookie prompts and similar things.

    • ivn@jlai.lu
      link
      fedilink
      English
      arrow-up
      20
      ·
      edit-2
      3 months ago

      It has some deal breaking limitations:

      • No filter list that can be updated, you have to update the whole extension to update filters. This adds delay as it has to go through Google verification process, they could even refuse some updates.
      • Not every type of rules are available on MV3, so it has to drop some filters.
      • No CNAME-uncloacking.