Please add a FAQ to explain users that disabling RFP is very bad
Starting with Tor Browser 13.0, we decided to lock privacy.resistFingerprinting
.
RFP is a very important setting. Disabling RFP makes you easily fingerprintable in a lot of ways, including hardware! Generally speaking, Mozilla is well aware of these fingerprinting vectors and continuously add even more. At the moment, the protection isn't granular, it's all or nothing (and I'm not saying it's bad - quite the opposite - it's the same philosophy of Tor Browser: normalize everything).
Also, when we send patches to Mozilla, we often gate them behind RFP. Setting RFP to false is like telling that you don't want a bunch of our patches.
RFP has usability issues (e.g., it constantly resets the zoom level, which can be a big accessibility problem). We're aware of that and it's in our roadmap.
We've received some feedback against our decision after the release, and we still get from time to time. I think we could have a FAQ about this.