Hacker News new | ask | show | jobs
by gruez 2 hours ago
Anti-fingerprinting measures with configurable knobs is always going to be a risky proposition because those options themselves end up being a fingerprinting surface. It's better to take firefox/tor browser's approach and have a common profile eg. "resistfingerprinting" to get crowd anonymity.
1 comments

This extension does not allow you to adjust how a given patch works - for the reasons you wrote. You are 100% right. This extension allows you to configure the availability of certain spoofed surfaces for specific sites. Moreover, this extension does not try to override the protections that Firefox uses, e.g. in the case of limits on the presentation of the amount of available RAM.

Your opinion is completely correct if we assume that most users will use Tor Browser. However, it is 2026, and it does not seem that Firefox will regain its position on the market. The idea behind this extension is to provide very basic (relative to what the browser manufacturer could do - and often does not do) protection for users of mainstream browsers. I use Helium and Zen myself, depending on the context of the work I do, but I am aware that most people will reach for a browser whose manufacturer sunsetted Privacy Sandbox a year ago.

>Moreover, this extension does not try to override the protections that Firefox uses, e.g. in the case of limits on the presentation of the amount of available RAM.

This seems contradicted by the screenshots, which lists options for "time", "canvas", and "screen". Firefox's RFP has protections for all of those. Not to mention it has "protections" for APIs that don't even exist on firefox.

https://developer.mozilla.org/en-US/docs/Web/API/Battery_Sta...