Quote from: Pamoldar on November 08, 2019, 08:28:04 PM

What is happening? I really do not like this cloudflare thing.
Somewhere I read theymos is too lazy to code a script that will save us from DDOS without cloudflare, my memory is not serving me well though.

You cannot just write a script to stop a DDoS. If it was that easy, every CMS system and OS would have it already implemented. DDoS works mostly by saturating your uplink; while a script on a server can still filter requests, it cannot reduce traffic before it reaches that server.

Quote from: Lauda on November 08, 2019, 08:33:11 PM

DoH is long overdue, but unfortunately has many downsides that weren't remedied properly. It's all good though, 99.9% of you guys are sheep.

It only has downsides.
1. Supporters say that it stops your ISP from snooping, but DoH would concentrate 99.9% of all requests at Cloudflare. If you do not trust your ISP, why trust Cloudflare? Because they promise not to spy? Yeah, sure.
2. Since DoH is just a HTTP request, every piece of software/malware can contact its own hardcoded resolver and ignore system DNS settings. That's a bullet into the head for most DNS based adware/malware filters. Yes, you can define your own resolver in Firefox, but how many average people will do that? Right now you block udp/tcp port 53 to stop access to resolvers except those you allowed.
3. If it would really be about securing DNS with encryption, Mozilla/Google/et al would support DoT which is already defined in RFC7858 which would smoothly integrate into current networks instead of risking to break a core functionality of the Internet.
4. DoT provides the same security as DoH, and still leaves users all the filter/blocking options DNS currently has. You would only enforce DoH if you want all user data concentrated at a single point, ripe for analysis, profiling, censorship, tracking and spying. There is no reason to trust Cloudflare more than your ISP, so the trust argument is entirely void.