The firefox bit has these:

> Disables native privacy and anti-tracking features

> Disables DNS-over-HTTPS

Why?

With DNS-over-HTTPS, your DNS queries are sent to Cloudflare (by default; it is configurable). Without it, your DNS queries are sent to your ISP. The question is which company you trust more with your DNS queries.

Given how often ISPs and/or countries do stupid things with DNS, I think DNS-over-HTTPS is a reasonable default. But some people don't trust Cloudflare with that info, so they use the ISP option instead.

Both are reasonable choices.

▲

MadameMinty 7 hours ago | parent [-]

With DNS-over-HTTPS, that is only for Firefox. Chrome doesn't do that.

▲

coldpie 6 hours ago | parent [-]

Interesting! More reading here: https://blog.chromium.org/2020/05/a-safer-and-more-private-b... Looks like they try to choose a D-o-H provider that is associated with your plain DNS provider, instead of just jumping straight to Cloudflare.

	▲	MadameMinty 6 hours ago \| parent [-]
		Yup, iirc Mozilla made a deal with Cloudflare to... not do that.

▲

cullumsmith 8 hours ago | parent | prev | next [-]

I prefer to let uBlock handle all the blocking. Also I run my own DNS server where I have my own blocklists and internal records etc.

▲

protoster 7 hours ago | parent | prev [-]

My guess for privacy and anti-tracking is that trying to resist fingerprinting is, ironically, very fingerprintable.