I hardly use the browser on my phone, maybe an hour a week so I don't get too carried away with whats best or extensions.
I'm not. Brave has aggressive fingerprinting but that comes at a cost; you might encounter captchas to solve more often than on FirefoxI was surprised by the “fingerprinting resistance” line.![]()
If I recall correctly, there is a way to get about:config in stable version of Firefox for Android. Then you can enable aggressive fingerprinting protection and get even better result than on Brave. Just be aware that it will impact the web browsing experience a lot.I believe that by changing a few settings (SecureFox/BetterFox) in about:config, Firefox users can improve their results slightly.
But that means using Firefox Beta.
I'm not. Brave has aggressive fingerprinting but that comes at a cost; you might encounter captchas to solve more often than on Firefox
If I recall correctly, there is a way to get about:config in stable version of Firefox for Android. Then you can enable aggressive fingerprinting protection and get even better result than on Brave. Just be aware that it will impact the web browsing experience a lot.
EnterReally?
I didn't know that. Can you explain how to do this?
TH.
When I open about:support (it works), I see that very few settings have been changed compared to my desktop Firefox.
chrome://geckoview/content/config.xhtml in Firefox address bar and enable general.aboutConfig.enable flag. Keep in mind about:config disappears once you close the app. However, settings should persist.Enterchrome://geckoview/content/config.xhtmlin Firefox address bar and enable general.aboutConfig.enable flag. Keep in mind about:config disappears once you close the app. However, settings should persist.
@Marko :)
Your hunch was right.
After adjusting a few settings and running the data through ChatGPT 5.3, here’s the updated table.
The AI has highlighted the modified values with an arrow at the top.
It also reduced site compatibility/stability by 1 percentage point, but I didn't look into it further because I'm a bit tired after making all these changes.
And AI reiterated that the biggest difference is due to uBo - Hard Mode + TLD.
Of course, the percentages are fictitious for the two selected browsers and aren’t generally applicable when compared to other browsers.
Maybe. But to me, that last site compatibility metric weighs more. What's the point if sites don't work?
As I already said, Firefox is customizable to the level no other web browser is. You can make it more hardened and locked down than any other web browser, including Brave. Though that all of that has a cost and it depends on you how much website breakage you're willing to take for the questionable success.@Marko :)
Your hunch was right.
After adjusting a few settings and running the data through ChatGPT 5.3, here’s the updated table.
The AI has highlighted the modified values with an arrow at the top.
It also reduced site compatibility/stability by 1 percentage point, but I didn't look into it further because I'm a bit tired after making all these changes.
And AI reiterated that the biggest difference is due to uBo - Hard Mode + TLD.
Of course, the percentages are fictitious for the two selected browsers and aren’t generally applicable when compared to other browsers.
I think it's better to use Hagezi's Most Abused TLD list rather than blocking all TLD except these few.Websites outside the 9 TLDs (com, org, net, eu, io, ms, gov, info, it) may not work.
You can add more TLDs.
With a single click, you can enable 3rd-party frames and scripts locally—that is, limited to that specific website—or even disable uBo for that specific website; you always have DNS-level filtering.
So there are many options available to restore functionality for that specific website.
As I already said, Firefox is customizable to the level no other web browser is. You can make it more hardened and locked down than any other web browser, including Brave. Though that all of that has a cost and it depends on you how much website breakage you're willing to take for the questionable success.
There's a reason why Firefox has these options disabled by default.![]()
I think it's better to use Hagezi's Most Abused TLD list rather than blocking all TLD except these few.