• moitoi@feddit.de
    link
    fedilink
    arrow-up
    58
    arrow-down
    7
    ·
    9 months ago

    Brave to end ‘Strict’ fingerprinting protection as it breaks owns ad revenue.

    • Pantherina@feddit.de
      link
      fedilink
      arrow-up
      6
      arrow-down
      14
      ·
      9 months ago

      No it literally breaks sites. I was using Firefox with Arkenfox user.js, basically Torbrowser, and nothing broke unless the site told me “your browser is not supported”. Braves strong defaults broke Github and more.

        • Pantherina@feddit.de
          link
          fedilink
          arrow-up
          1
          arrow-down
          3
          ·
          9 months ago

          Not much Brave can do there? I dont know what they did. You are probably better off with UBO and NoScript (both MV2 btw).

          But everyone is escalating about Brave removing a broken feature as if they where getting worse or something. The feature was broken, they removed it. Thats it.

      • AnonTwo@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        9 months ago

        Was strict the default? I’d assume the standard would be the default.

        I’d imagine if you were using strict you want the sites to break because you absolutely do not want fingerprinting. That kindof restriction usually comes with the breaking being expected.

        • Pantherina@feddit.de
          link
          fedilink
          arrow-up
          1
          ·
          9 months ago

          Yes probably. I have no idea what they did though, because Arkenfox / Torbrowser doesnt break anything.

          Noscript and ublock origin are both MV2. But Brave wants to keep supporting MV2.

          So I think they should not try implementing stuff extensions already do better, but at the same time something like this is the only way if they want to also go full MV3 and save themselves a lot of maintenance