262
Brave to end 'Strict' fingerprinting protection as it breaks websites
(www.bleepingcomputer.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jan 2024
262 points (96.1% liked)
Privacy
32008 readers
1009 users here now
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
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
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.
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.
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