• nomemory@lemmy.ml
    link
    fedilink
    arrow-up
    18
    ·
    2 years ago

    By reading through the article I see that Firefox is going to support adblocking techniques, while Chrome is going to remove them.

    Am I missing something?

    • Ephera@lemmy.ml
      link
      fedilink
      arrow-up
      12
      ·
      2 years ago

      Yeah, I don’t get why the rest of the comments here are shooting against both. Firefox is 100% doing the right thing here.

    • Seirdy@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      2 years ago

      The reality is more nuanced than this. Wrote up my thoughts on my blog: A layered approach to content blocking.

      Strictly speaking about content filtering: declarativeNetRequest is honestly a good thing for like 80% of websites. But there’s that 20% that’ll need privileged extensions. Content blocking should use a layered approach that lets users selectively enable a more privileged layer. Chromium will instead be axing the APIs required for that privileged layer; Firefox’s permission system is too coarse to support a layered approach.

    • Echedenyan@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      2 years ago

      LibreWolf is a light Firefox fork which is dependent of upstream and hard code changes.

      Tweaking configuration, applying little patches, re-building in custom setup and re-branding won’t be enough.

      The best would be promoting or helping Pale Moon development to not doing the same in addition to arising that an HyperbolaBSD main developer and author is working with them to develop their browser based on UXP.