A browser privacy showdown has been brewing for a while.
  • @nomemory
    18•2 years ago

    deleted by creator

    • Ephera
      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
      1•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.

    • @tristanOP
      13•2 years ago

      @Shishimaru, what do you use instead?

      (The article notes that Firefox is going to continue to support a wide ranger of ad-blocking, while Chrome is not.)

      • @sproid
        6•2 years ago

        He went back to Internet Explorer

      • @yeolsongarak
        1•2 years ago

        I thought the answer was going to be Falkon, but it ended up being an ad response…

        • @cheer
          3•2 years ago

          Sorry to hear that