dngray:
“degoogling” nonsense
Everybody has their own privacy goal. Who are you to tell them this goal is nonsense? Also I used it as an example, not as an argument for ungoogled chromium. I don’t use it myself.
Some browsers are more fingerprint-able than others.
opened 11:54AM - 30 Nov 23 UTC
feature/shields/fingerprint
OS/Desktop
## Description
The Client Hints API, both JS and headers, is active and leaks … fingerprintable information.
I would expect, especially when opting in for aggressive fingerprint resistance, that for example my exact OS version would not be reported.
## Steps to Reproduce
1. Visit https://browserleaks.com/client-hints
2. See leaked information
## Actual result:
<img width="944" alt="image" src="https://github.com/brave/brave-browser/assets/40439946/9d9a60e0-4554-41c2-bb2e-e50e7011eb5d">
## Expected result:
Disabled API or no results (like in Firefox)
<img width="941" alt="image" src="https://github.com/brave/brave-browser/assets/40439946/54e74594-71d7-4141-af3b-e0e6926688d7">
## Reproduces how often:
Default browser behaviour
## Brave version (brave://version info)
1.60.125 Chromium: 119.0.6045.199 (Official Build) (arm64)
9c1f9e267d7ef50aefbe434e616e05290536926b
macOS Version 14.1.1 (Build 23B81)
## Version/Channel Information:
- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Not tested
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? No
- Does the issue resolve itself when disabling Brave Rewards? No
- Is the issue reproducible on the latest version of Chrome? Yes, but that's wanted in Chrome.
That’s all I’ll say for now. No point in addressing the other comments you’ve made in bad faith.