diff --git a/3.3-Overrides-[To-RFP-or-Not].md b/3.3-Overrides-[To-RFP-or-Not].md
index 60db006..ea5214b 100644
--- a/3.3-Overrides-[To-RFP-or-Not].md
+++ b/3.3-Overrides-[To-RFP-or-Not].md
@@ -60,6 +60,12 @@ Arkenfox's primary objectives have always been security, privacy and mitigating
    - RFP randomizes canvas to catch naive scripts (most scripts are naive with canvas)
    - RFP contains timing mitigations as a bonus against many side channel attacks
 
+**_Do not listen to random [non-experts](https://old.reddit.com/r/firefox/comments/wi9vee/firefox_and_fingerprinting/ijae7ow/)_**
+
+- 🔹 RFP doesn't require a crowd or care about Tor Browser when it comes to naive scripts
+- 🔹 RFP can't make fingerprinting worse, you are already unique if you do nothing
+- 🔹 RFP has a net privacy benefit (see the resistance points above)
+
 So if a fingerprinting script should run, it would need to be universal or widespread (i.e it uses the exact same canvas, audio and webgl tests among others - most aren't), shared by a data broker (most aren't), not be naive (most are) and not be just first party or used solely for bot detection and fraud prevention (most probably are) <sup>1</sup>.
 
 <sup>1</sup> That's not to say that fingerprinting is not a threat and won't become more widespread and sophisticated.