I’m not in favor of this at all. Firefox has always been on top of new privacy features, like their containers and now their new profile UI, total cookie protection, canvas randomization, blocking trackers by default, DoH integration by default, URL tracking parameter stripping, HTTPS only mode, and of course their privacy features upstreamed from Tor browser. It’s telling how much Brave has to add (and remove) to chromium to approach the privacy features of stock Firefox, when most “private” Firefox forks are just changing some settings.
Plus, it’s the default browser on most Linux distros, so having a guide on how to configure it to be more private is useful I think.
Even their telemetry (which you can easily disable) is privacy-preserving. They utilize OHTTP and Prio which is their protocol for splitting data between two parties (currently an IETF draft). As pointed out earlier, Arkenfox doesn’t consider the telemetry to be a privacy concern as well. I don’t think some optional search engines change that.
Just this year, Mozilla came out with CRLite, a fast and private certificate revocation protocol. They’re genuinely doing research and having a positive impact on privacy.
They’re also working directly with Tor browser of course and upstreaming improvements from there, so you can enable privacy features from Tor browser through the RFP setting. Firefox is genuinely really good for privacy.