Swing and a miss, bud.

I've tried all three and I currently use the free ControlD Ads & Tracking DNS resolver and I've been very happy with it. It filters a fair amount of garbage domains in my experience and I don't want to spend time finely tuning the blocklists a DNS resolver uses. I use it over Adguard DNS because I noticed it blocks a few more domains in my observation.

I think most people talk about NextDNS because of the level of customizability it offers, if you want to finely tweak the blocklists and whatnot your resolver uses. It also has a pretty good web interface showing you all kinds of stats and whatnot.

You also have to keep in mind that ControlD is newer in comparison to either NextDNS or Adguard DNS by a few years, so there's likely less people discussing it as it's a little less known.

Absolutely gutted the Lionesses lost in the final, but upon reflection upon the entire tournament it is an absolutely massive achievement to finish as runners up. This will inspire a whole new generation of grassroots players and women's football fans, and hopefully inspire England to push on, learn some lessons, and hopefully get back there again in the next tournament. The Women's World Cup overall has been a truly amazing tournament and a great showcase and celebration of women's football. I'm sad it's over.

If you enjoyed the tournament, check out the Women's Super League (WSL) where a lot of these international players ply their trade domestically.

Ah the classic naïveté of the "nothing to hide" argument.

Regardless of the presented reason, it is right that people question and are cautious about increased surveillance. Some people are willing to capitulate to more and more monitoring very easily. Privacy is important.

And FF containers are still no match for advanced fingerprinting.

The only way to protect against advanced fingerprinting is to use the TOR Browser or Mullvad Browser, to blend in with everyone else who shares the exact same fingerprint using those tools. The best you can do outside of those is to protect against less advanced scripts.

I mean, I consider Mastodon pretty "customizable" in the sense that you state. It's easy to follow individual hashtags surrounding specific topics, groups that people use to post about a specific topic or individual users. My home timeline is pretty much all topics I'm interested in due to who and what I follow.

Similar to Lemmy really. Your subscribed feed should be exclusively topics that interest you from the communities you subscribe to.

I am absolutely not, but this may have changed as I don't have access to real-time information as my knowledge was last updated in September 2021.

Yes. In fact, using DNS-based blocking solutions are pretty much the only way to protect against first party trackers that use CNAME cloaking tactics if you're not using a Firefox browser with UBo, since Chromium browsers have no ability to defend against this type of attack (with the exception of Brave as they implemented their own method of protecting against this with their Shields system.)

Encrypted DNS doesn't really do much for privacy. It does, however, accomplish two main things:

• Ensures the authenticity of the DNS server you're receiving a response from due to the certificate exchange.

• Preserves the integrity of the response as it would be difficult for it to be tampered with in-transit.

The domain names you visit are leaked in plain text regardless of your DNS provider and how you connect to them via the "client hello" process of TLS, specifically the Server Name Indication (SNI) portion. ISPs could, in theory, use this to see which domains you're visiting, even if you're using encrypted DNS, but not the specific pages within the domain.

Note that there are mechanisms like ECH (Encrypted Client Hello) and ESNI (Encrypted Server Name Indication) that attempt to solve the domain name leakage issue, but each require domains that wish to support these technologies to include an entry specific to those in their DNS records to facilitate key exchange for the encryption to be viable. You'll also need a DNS client that supports ECH/ESNI. Very few domains and clients presently do this, meaning it is almost certain all/the vast majority of your visited domains would be transmitted in plain text at this point in time.