afontenot
vendor.js preferences
@pyllyukko is maintaining a great user.js file that holds Firefox configuration. It's nothing that affects the actual build but the preferences used at run-time. It could be utilised to override some factory defaults considered bad. However, there are some prefs that break functionality or web pages. Changes in the provided vendor.js would set the package defaults but still allow users to change settings via user.js or prefs.js.
see also A brief guide to Mozilla preferences
Akin to the aforementioned script (and its more usable version which I would choose) is also @Thorin-Oakenpants & @earthlng and their user.js which I find better structured and easier to maintain.
In any case both feature complementary discussion as to how to handle privacy/security, with a strong focus on fingerprinting it seems − a threat model that forces to break a lot of functionality. I guess it all depends of your definition of 'clean', but I suggest not to go as far.
The two user.js projects here allow us to stay reasonable in what we want to disable by default, and point to them for more involved choices. We could ease their integration in the PKGBUILD though, maybe by letting a placeholder and proper comments/doc.
