-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow users to disable APIs that intentionally identify the browser as Brave #8757
Comments
The whole thing is paradoxical, unclear and contradictory. |
This is not correct. Brave doesn't appear in the UA for web compat reasons. Brave makes many changes in the browser that it already looks / behaves very different from chromium, so reporting brave in the UA would not have any change in the browser's fingerprintability (e.g. the other changes brave makes are consistent across all brave instances per platform, so changing the UA in a way that was also consistent across all brave instances per platform would not affect the anonymity sets at all). |
You should have implement previous backlog by giving an option to change it. The whole purpose of using Brave seems worthless now. Some websites have started blocking Brave intentionally. |
Which ones? |
@ryanbr can you add a fix for the above, with another remove isBrave for the above? |
Does this error message come from kodekloud.com domain? @arpitjindal97 |
When you try open Labs session on kodekloud.com then you will see this error |
If you add Does that help? @arpitjindal97 |
Apologies for the delay, managed to recreate the issue, @arpitjindal97 give it 24-48hrs the update will fix this issue with shields up. |
Thanks @ryanbr , new update fixed the kodekloud issue. Waiting for a full fledged solution. |
Yeah, tried reaching out to them via twitter, got no response @arpitjindal97 |
Currently brave allows sites to determine if its brave by querying a Brave-specific API (
navigator.brave.*
). This was done in #8216 to:However, it would be nice to have a way for users to disable this if needed, either per site in shields, or globally through a flag.
The text was updated successfully, but these errors were encountered: