• FurtiveFugitive@lemm.ee
    link
    fedilink
    arrow-up
    3
    ·
    7 days ago

    How would you say it’s a turd? I assume because it’s still chromium based, but I don’t want to put words in your mouth.

    It’s my browser of choice for my work computer but I do run Firefox at home and on mobile.

      • Azdalen@beehaw.org
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        6 days ago

        which is why vivaldi purposefully added a blocker engine into the browser to side-step the extension limitations. It includes some default lists, as well as allows you to add your own with support for ublock, adguard, and ABP syntax and scriptlets. then all you need to do is goto https://github.com/uBlockOrigin/uAssets and add whatever offical asset lists you want… is it as good as FF + uBO, no, but it is something.

        • Corgana@startrek.website
          link
          fedilink
          arrow-up
          1
          ·
          6 days ago

          I found a Vivaldi blog post on this topic from 2022: https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/

          Will the Vivaldi Ad Blocker be affected by the Manifest V3 changes?

          I made some architectural choices early on that I believe should keep it functional, regardless of the Manifest V3 changes. Of course, there is always a possibility that the underlying Chromium architecture will change now or in the future, forcing us to do some extra work to keep this working. ​> Hopefully, a more in-depth description of the architecture and some of the facts surrounding the Manifest V3 changes should help to show why I believe that our implementation is safe for the time being.