@Iron Heart Tor Browser says to not change default settings because it is already providing the privacy protection to help its users to remain anonymous and its effective at that for the most part. More often than not if a certain user tinker in about:config settings, without knowing what is he doing, that user often disables certain protections without even noticing it. I don’t know what the hell you said that came in personal attack category. About Browser fingerprinting – I use two phones currently. First one is fairly new as Android 11 is supported on that model and the second one is on Android 5 and yeah its ancient in today’s world, but because I was curious how it would perform after years I gave it a try. I kicked things off in January last year and so I first ran Play Store on it and found some popular apps and then specifically tried to found reviews from this device model but I didn’t find any latest reviews within a year – no surprise there. Now if I use a browser in that phone and updated one at that, by your definition because of default settings, I can safely say I would stick out very easily in terms of fingerprinting as that phone doesn’t even support 4G and it would be visible in connection type without forgetting old Android version, up to date Browser and other entropies. To make it stop I use RFP on both my devices in Firefox and both produce same fingerprint in terms of User Agent, connection type and more. That’s why your definition of Browser fingerprinting does not hold its ground in the vast ocean of different Device model from various manufacturers without forgetting different roadmap of OS updates. Default settings can only be good if they are done properly, in Brave’s default setting it introduces random values in some test but reveals true values in User Agent, connection type and that introduces more entropy which easily reveals its not a Chrome even if user agent is same and so different device models and all of a sudden Brave users are not private anymore. Bromite hides user agent but still reveals connection type because its not just a Brave or Bromite thing, its the Chromium problem, and the way some toggles have been removed from Chrome like WebGL, WebRTC it leaves hole for more entropy, not now but in future as well. When you say you’re giving more information or increasing your fingerprint by using RFP, its not as simple as that. Every browser needs to provide some sort or value whether static like Firefox or randomized like Brave, but its only effective, to a certain extent, if it can’t be linked back to the Browser type in the first try and it doesn’t matter how much someone is altering values if its revealing main things in the first place – its like preventing yourself in winter by only opening your door and window all the time with all sorts of clothes on. By using certain protections, the whole fingerprint of two different models can look like same. Now its not perfect like Tor, but its way too far ahead of Chromium browsers(default or modified) and even default Firefox. Just don’t ask why I’m using an old device because I’m not using an old device but rather a new one and an old one.