Chameleon does not seem to be enough. Or do you have some pointers how to configure it?

The EFF site showed two fingerprint ids that were completely unique for my browser: window size (because of my dock) and the http-accept headers (because of my language selection). That's with FFs fingerprint-resist option enabled. Chameleon can spoof those, which is great, and it gives access to the fingerprinting option which I think FF does not expose properly outside of about:config. So it should greatly reduce my identifiablity, but according to the site it does not help much, even if the specific categories are now almost unique. Like they explain, the combination seems to be the problem, or maybe they are not exposing the category that gets me.

Edit: Okay. The solution seems to be: Chameleon with most of the options enabled, so as much spoofing as possible, but without activating FF's fingerprint-resist option. Probably sending no data is worse than sending spoofed data!

+ Ublock of course.

I’ve not compared the two in any great length, but another add-on that aims at protecting against fingerprinting is CanvasBlocker.

Are there any catalysts to reverse our course?

We just need to make sure the browser suppliers are in total opposition to the surveillance capitalism and personalised advertising industry.

So while Chrome is such a dominant browser? No. It’s not gonna happen. Google will keep writing “inadvertent errors” that exempt their own tracking cookies from user instructions to delete them.

https://lapcatsoftware.com/articles/chrome-google.html

Google owning the dominant browser and mobile OS is a travesty for privacy. What we really need is a consortium of companies to rally behind FireFox for mutual benefit, like how Linux is done

Most of Firefox funding comes from Google

Yes, but having companies/entities other than google funding them would reduce the "say" google has in the browser design and implementation.