Req: Option to disable first party fingerprint randomization

[rugabunda]

Ghacks explains this somewhat here, UA spoofing is best left to privacy.resistFingerprinting, whereas the other features are great. Please offer an option to disable your first party fingerprinting system, according to ghacks, it impedes upon firefoxes perfected and inbuilt tor based fingerprinting protection by raising entropy.

I think that means thanks to tors setup there are more users who all look the same than look random, even the window size, and because random is unique as it gets, though indeed never the same twice... some things cant be randomized, so you have a mix of both random and static, and depending upon hundreds of possible variables, higher entropy has a tendency to makes you more unique. Thus it has the potential to make marketers more money. And otherwise, if you want to do the years of work firefox/tor put into it, you have to re-invent the wheel. So if you are going to add such a feature, please make it optional.

If it does not already, if your addon simply automatically enabled/disabled this feature by detecting the privacy.resistFingerprinting setting, and suggested users to enable that, that would be nice also.

[rugabunda]

Via Ghacks: arkenfox/user.js#395 (comment)

You've spent a lot of time with containers etc, I've spent far too much time on FP'ing (5 or 6 years). Trust me, you do not need to waste resources on this. Solutions already exist, especially the RFP pref one, which can do things that extensions cannot, since its baked into the code. Not only that, but it has patched long standing holes in eg navigator (which only applies when RFP is enabled).

TL;DR: waste of time

it's extremely complicated and takes a lot of work
its already been done, a thousand times
is already available in Firefox behind a pref
or an aspect of it like canvas has special dedicated extensions
deviation from RFP can easily render RFP useless (so your features may just screw things up )
    we even have an RFP alternative section in the user.js, all inactive, so users know these should be at default when using RFP
takes away resources from the core functionality/purpose of TC"