4 ms·

Mozilla is optimizing for a weighted sum of privacy and revenues from Google (who still account for >90% of Mozillas income). Therefore manually removing all G

• nextos 8y ago
  I agree. I also try to keep it simple to avoid too much maintenance hassle. Sadly about:config is too imperative, so you need to explicitly undo changes. I wish it was like regular dotfiles. In any case this is in my user.js: user_pref("datareporting.policy.dataSubmissionEnabled", false); user_pref("privacy.trackingprotection.enabled", true); user_pref("media.autoplay.enabled", false); Along with ublocko and httpseverywhere, that covers a lot without breaking mostly anything. A quite famous user.js hardening project is https://github.com/pyllyukko/user.js https://github.com/pyllyukko/user.js. But I've found that keeping such a complex configuration functional requires a lot of constant effort.
• boomboomsubban 8y ago
  >who still account for >90% of Mozillas income). You say still, but this will be the first time in a few years that will probably be true. The details of the Google deal aren't public, but I doubt it forced them to spend the past few months secretly hiding Google tracking into the browser.