Thorin has asked me to post this reply:
Arkenfox switched to dFPI as soon was was feasible - that was from memory back in FF102. Arkenfox switched from RFP to FPP as soon as was possible - that was back in FF128. Arkenfox was an early adopter of CRLite which reduced dependency on OCSP (and recently did away with the OCSP fallback hard-fail check entirely). Arkenfox has removed all the pref changing that wasn’t a privacy concern (thus reducing hoops for users to jump through, or causing breakage/usability). Arkenfox has sane defaults and is practically FF with ETP Strict and site data sanitizing and a handful of other changes. We’ve even restored the default to maintain history and downloads (these are not website accessible). It is a template after all, so the less destructive from the start, the better - and users who want to sanitize history/downloads for disk/opsec can do so. Arkenfox lists items NOT TO CHANGE or mess with. Arkenfox list optional items but WARNS they break shit. Arkenfox educates those who read it.
LW, Phoenix etc break shit left right and center. Phoenix is busy trying to add exemptions everywhere it can to unbreak shit in a misguided attempt to use RFPTargets - that’s not how fingerprinting works. Betterfox is full of churn, noise and snake oil items such as speeding things up - not saying the info is incorrect, but the claims of speed ups - there is no one size fits all) and so on.
ARKENFOX IS FUCKING UNEXTEREME - stop spreading the bullshit. ARKENFOX IS SUPER STABLE and only needs 3 or 4 updates a year
All hail the pants!