3 ms·

So... then disable them using the instructions on that github gist that you already linked? What exactly is the gripe here? There is no need for a fork when you

So... then disable them using the instructions on that github gist that you already linked? What exactly is the gripe here? There is no need for a fork when you've already disseminated the information needed to rectify the problem. I don't know what else anyone would consider adequate -- web advertising and tracking is not going to magically go away or diminish just because browsers have less features. Focus on one thing at a time, please.

JohnFen 7y ago
> I don't know what else anyone would consider adequate I'd consider opt-in rather than opt-out to be adequate.
- cycloptic 7y ago
  This is splitting hairs. You can easily use (or make) a downstream distribution of Firefox where that is the case. No forking required, just ship a default config. This still would be a reasonable course of action even if your real concern is what is adequate for the wider community, not just for yourself. Threatening to switch to another browser isn't going to help because anything you switch to at this point is going to be a fork of Chrome or Firefox, probably with additional ads and tracking added from the other downstream vendor. Like it or not this is the funding model of the web. Edit: I haven't checked in a while but I believe there are actually already several privacy-focused forks of these browsers that ship with the default configs changed to remove ads and tracking, among other things.