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

  • brucethemoose@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    3 months 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.

    • America@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      3 months 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

      • ruby@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months 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?

      • brucethemoose@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 months 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.