Hello Brave dev team
In view of these tests carried out in several browsers, what is being done by the Brave team of developers to fix them and when will these possible improvements in security and privacy be ready? Of course, if the tests have any relevance and importance to the Brave!
More information follows:
One, two are solved in nightly builds like HTS cache ( the first red cross).
These tests are done on default settings and not for highly hardened settings. If you hardern the brave browser to its limit via changing various flags in brave://flags, some of them will be solved automatically.
The dev of this particular website is himself an engineer at brave. Meaning they know where they lack in certain areas like screen fingerprinting and may try to improve the browser in this sector
https://privacytests.org/about.html (see last point)
Re What is Brave doing
General Ref. material:
–
–
Shields v1 illustrations:
–
Shields v2 illustrations:
–
Brave History, Papers, and Plans
Brave AMA (Ask Me Anything) Series
Brave, Fingerprinting, and Privacy Budgets
Brave Release Schedule - (Chromium Release Schedule)
Comparing the Network Behavior of Popular Browsers on First-Run
Ephemeral Third-party Site Storage
First-Party Sets: Tearing Down Privacy Defenses Just as They’re Being Built
Improving Privacy By Improving Web Compatibility
Example: Privacy And Competition Concerns with Google’s Privacy Sandbox (Jan. 26, 2022)
About that: “Google resumes shoveling stuff into its ‘Privacy Sandbox’ (Mar. 29, 2022; The Register)”
–
Brave Browser - GitHub - Deviations from Chromium (features we disable or remove)
–
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
