2 ms·

The firefox bit has these: > Disables native privacy and anti-tracking features > Disables DNS-over-HTTPS Why?

• cullumsmith 1mo ago
  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.
• coldpie 1mo ago
  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 1mo ago
    With DNS-over-HTTPS, that is only for Firefox. Chrome doesn't do that.
    • coldpie 1mo ago
      Interesting! More reading here: https://blog.chromium.org/2020/05/a-safer-and-more-private-browsing-DoH.html 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 1mo ago
        Yup, iirc Mozilla made a deal with Cloudflare to... not do that.
• protoster 1mo ago
  My guess for privacy and anti-tracking is that trying to resist fingerprinting is, ironically, very fingerprintable.