For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.

What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.

  • rklm@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    2 days ago

    I did my testing before the AI features were implemented, and I tested a variety of custom profile settings for firefox (and floorp and librefox) and custom chrome flags for ungoogled chromium (and brave)…

    Granted, I was using benchmarks, but the differences are somewhere around 15-30% on my machine on Arch

    Edit: These are the benchmarks I ran

    • spaghettiwestern@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 days ago

      Interesting running those… Haven’t had to worry about benchmarks on my system, both Chrome and FF are plenty fast. I do wonder how the performance of Chrome with ads would compare to Firefox with the same ads blocked? Every once in a while I use some one else’s computer and can’t believe how many animated ads show up on pages I frequent.

      Do you just put up with the ads or block them another way?

      • rklm@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        MV2 has always worked on ungoogled chromium, so I just use uBo. I agree with most folks that ads are not an option XD