Never use Chrome, but there are some reasons to use a Chromium fork browser.
On privacy, just using Pale Moon gives them like 10 bits of signal to id you with on top of all the other things they can use. That's huge. Brave looks like any other Chromium except with fingerprint randomization for lots of things.
Also the more Chromium forks there are the harder it is for Google to make changes because they have to keep the forks from splitting off on their own.
For example with the new manifest to limit adblocking, if Brave/Edge/Vivaldi/Opera don't accept that change then Google's 75% market share drops to maybe 60% or something like that and those others are virtually identical except with better features so it's easy for people to switch.
Google has already delayed manifest v3 by 4 months so far for this reason. They say "intently monitoring comments from the developer community to help inform our timelines" and what that means is "finding some way to do it without losing the forks".
Pale Moon can be setup and configured so you don't give out any identifying information. Unlike Brave. Pale Moon also does fingerprint randomizations, instead of fingerprint uniformity, but PM does it with so much more stuff than Brave.
The more chromium forks there are, the greater hold google has on the internet, and fingerprint uniformity only works by restricting usage of the browser. No customizations, no addons, no nothing. It's the wrong way to tackle anti-fingerprinting.
Pale Moon didn't score as well as a new Brave profile, with Pale Moon having a non-randomized canvas, GL, number of cores, and audio fingerprint whereas in Brave these are all randomized. Pale Moon screen size approximates the actual screen size whereas in Brave reported screen size is not similar to actual screen size.
But it doesn't even matter that Brave is more private by default. They all give out so much info that if you want to have multiple personas it's best to use different browsers for each; use Pale Moon and Brave.
You show that you don't really know what you're talking about sadly. coveryourtracks doesn't work on Pale Moon (Bad Request
Request Line is too large (8192 > 4094), which is why I left that one out in my post here about fingerprint tests..
"canvas.poisondata (true/false, v25.6+): Controls whether to mitigate browser fingerprinting through canvas rendering specifics.
This preference, when true, will poison data read from canvas areas with humanly-imperceptible variations in color and lightness.
Defaults to false; accurate reading of data is generally preferred, and poisoning severely impacts performance of reading data from canvas." -from 2013
They also randomize the addon order, and other things.
Screen-size spoofing and such can easily be circumvented, since most code "resisting" such fingerprints don't do enough (https://archive.is/kN0D5).
I do agree about compartmentalization, but one should use the best privacy and customizable browser as a main one, and use LibreWolf for the few sites that insists on implementing the latest google experimental "standards", and those "standards" only. Brave is the least worst google chromium browser, but it's still a google chromium browser..
Never use Chrome, but there are some reasons to use a Chromium fork browser.
On privacy, just using Pale Moon gives them like 10 bits of signal to id you with on top of all the other things they can use. That's huge. Brave looks like any other Chromium except with fingerprint randomization for lots of things.
Also the more Chromium forks there are the harder it is for Google to make changes because they have to keep the forks from splitting off on their own.
For example with the new manifest to limit adblocking, if Brave/Edge/Vivaldi/Opera don't accept that change then Google's 75% market share drops to maybe 60% or something like that and those others are virtually identical except with better features so it's easy for people to switch.
Google has already delayed manifest v3 by 4 months so far for this reason. They say "intently monitoring comments from the developer community to help inform our timelines" and what that means is "finding some way to do it without losing the forks".
Pale Moon can be setup and configured so you don't give out any identifying information. Unlike Brave. Pale Moon also does fingerprint randomizations, instead of fingerprint uniformity, but PM does it with so much more stuff than Brave.
The more chromium forks there are, the greater hold google has on the internet, and fingerprint uniformity only works by restricting usage of the browser. No customizations, no addons, no nothing. It's the wrong way to tackle anti-fingerprinting.
You're always giving out identifying information. What matters most is how you are using a browser, and you can check with something like:
https://coveryourtracks.eff.org/
Pale Moon didn't score as well as a new Brave profile, with Pale Moon having a non-randomized canvas, GL, number of cores, and audio fingerprint whereas in Brave these are all randomized. Pale Moon screen size approximates the actual screen size whereas in Brave reported screen size is not similar to actual screen size.
But it doesn't even matter that Brave is more private by default. They all give out so much info that if you want to have multiple personas it's best to use different browsers for each; use Pale Moon and Brave.
You show that you don't really know what you're talking about sadly. coveryourtracks doesn't work on Pale Moon (Bad Request Request Line is too large (8192 > 4094), which is why I left that one out in my post here about fingerprint tests..
and Pale Moon do randomize/poison the canvas data (https://forum.palemoon.org/viewtopic.php?f=24&t=3357&p=19126&sid=a96d404e4e2fc7c7d66c4a6adf13ea32#p19126):
"canvas.poisondata (true/false, v25.6+): Controls whether to mitigate browser fingerprinting through canvas rendering specifics. This preference, when true, will poison data read from canvas areas with humanly-imperceptible variations in color and lightness. Defaults to false; accurate reading of data is generally preferred, and poisoning severely impacts performance of reading data from canvas." -from 2013
They also randomize the addon order, and other things.
Screen-size spoofing and such can easily be circumvented, since most code "resisting" such fingerprints don't do enough (https://archive.is/kN0D5).
I do agree about compartmentalization, but one should use the best privacy and customizable browser as a main one, and use LibreWolf for the few sites that insists on implementing the latest google experimental "standards", and those "standards" only. Brave is the least worst google chromium browser, but it's still a google chromium browser..