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.
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 3.12K Posts
- 78K Comments
- Modlog
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