Hacker News Reader

DNScrypt is easy to block, therefore it can't further the privacy-for-all cause.

This is certainly a valid argument, though two of the other solutions (plus dns over tls) avoid this issue as well.

How does DoT avoid this issue? IIRC, DoT runs over port 853, which is trivial to block.

I am pretty sure that the client can use a bridge to connect.

And that's DoH. A DoT-over-HTTPS proxy if you will.

And for HTTP/1.1 it should use WebSocket for a persistent connection, but probably it already targeted HTTP/2.