Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Brave Software has announced plans to deprecate the 'Strict' fingerprinting protection mode in its privacy-focused Brave Browser because it causes many sites to function incorrectly.
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.
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
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.
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