> All this makes me think that such brute force cleanup in > about:config may be possible for other Firefox clones.
Very interesting. Thanks for the time your putting into this. If we can determine exactly which changes were the one that fixed the problem, I think asking for those values to be the default in privacy-minded FF derivatives like Icecat and Abrowser would be a reasonable feature request. It might be worth requesting the same of Mozilla, since that would benefit all downstream forks, but I wouldn't count on them caring... > However as I > haven't read what each setting does, it may have some other > (probably negative) effects. Perhaps we should read about all that > and come up with settings which are both private and don't affect > functionality (if that is possible). I agree that we'd be better off determining the minimum set of values that need to be zeroed to prevent background chatter will be better than zeroing all of them, but what you've found is a great starting point. A binary-search-like approach of zeroing groups of values containing URLs might help identify the culprit(s). Another thought I had is to compare the about:config for Icecat and Tor Browser and see if changing some of Icecat's values to match that of Tor Browser can reduce background chatter. I'm in the middle of a busy couple of weeks, but I'll try to start hepling you on some of this soon.
