Firefox says it will keep supporting uBlock Origin even as Microsoft Edge and other Chromium browsers phase it out under Manifest V3.

  • Victoria@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    313
    arrow-down
    5
    ·
    4 days ago

    If they ever stop supporting it I will continue to use the last version to support it, any website that breaks compatibility with this Firefox version can get fucked.

    • brucethemoose@lemmy.world
      link
      fedilink
      English
      arrow-up
      193
      arrow-down
      5
      ·
      4 days ago

      That’s a significant security risk, unfortunately.

      If that happens, I’d suggest a fork with a built in blocker, one that still gets security patches from upstream Firefox.

      • [email protected]@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        116
        ·
        4 days ago

        Exactly. Ublock origin is notable only for being part of 0 ad companies and 100% trustworthy. The blocking lists are universal. If it’s built into the browser, you’re golden

        • brucethemoose@lemmy.world
          link
          fedilink
          English
          arrow-up
          58
          arrow-down
          1
          ·
          4 days ago

          Well…

          With a fork, one is very dependent on the browser dev. Not just on their benevolence, but on their security practices too. And on them pulling in upstream security patches, quickly.

          TBH, this is why I do finance stuff on vanilla Firefox. I love browser forks, I really do, but I’m a bit more cautious with them, too.

            • brucethemoose@lemmy.world
              link
              fedilink
              English
              arrow-up
              11
              arrow-down
              1
              ·
              3 days ago

              True, sometimes. But they don’t have the sheer manpower dedicated to security that Mozilla has, nor the institutional policies that try to mitigate losing a key/account or something like that. Also, technically, vanilla Firefox is first to get the zero-day patches before they filter downstream.

              Not that the forks are dangerous or anything, generally.

        • ruby@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 days ago

          i mean… blocking lists are universal, but the other features ublock offers are not - i’m making heavy use of ublock’s dynamic filtering panel and per-site switches. one important thing i use ublock for is to whitelist which sites get javascript permissions and to get rid of remote fonts to make pages more readable. those features need manifest v2.

          if firefox drops manifest v2 and you’re relying purely on those inbuilt blocking lists then you might as well use the manifest v3 version of ublock without seeing a difference, right?

          • WhyJiffie@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            3 days ago

            if firefox drops manifest v2

            I think they said they will go out of their way to keep the extension APIs in Mv3 that uBlock needs

          • amorpheus@lemmy.world
            link
            fedilink
            English
            arrow-up
            4
            ·
            3 days ago

            you might as well use the manifest v3 version of ublock without seeing a difference, right?

            Can confirm, I was thinking about switching off of Chrome due to this but since I don’t use the custom stuff (much) I’m not noticing a difference with the v3 compatible “light” version of uBlock Origin.

    • anon_8675309@lemmy.world
      link
      fedilink
      English
      arrow-up
      34
      ·
      4 days ago

      I’ll just spend my reading time reading more books than I do now. Forcing me to look at ads will not work.

      • WhyJiffie@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 days ago

        librewolf does not have much developer capacity to maintain such heavy patches. you may remember some chromium forks telling they will maintain a patch when google completely removes this API from chromium, but it seems none of them will follow through. I can’t really fault them because it is likely a gargantuan task. but I’ll fault them for claiming something they (should) have known they can’t deliver. but my point is if vivaldi and others can’t keep it, how could librewolf?