@dakami @taoeffect "dnscrypt sacrifices caching" is demonstrably false
-
-
Replying to @bitbbq
@bitbbq@dakami@taoeffect Yes and no. Responses cannot be cached by an intermediary resolver.1 reply 0 retweets 0 likes -
Replying to @jedisct1
@jedisct1@bitbbq@taoeffect precisely, and most DNS lookups are hosted out of intermediate caches2 replies 0 retweets 0 likes -
Replying to @dakami
@dakami Do you have a citation for this claim?@jedisct1@taoeffect@davidu3 replies 0 retweets 0 likes -
Replying to @bitbbq
@bitbbq@jedisct1@taoeffect@davidu if 90% of queries are hosted at intermediate dnscrypt == 10x load. It's way more than 90%2 replies 0 retweets 0 likes -
Replying to @dakami
@bitbbq@jedisct1@taoeffect@davidu also, what, you're gonna add a per-query crypto dependency to the root servers?1 reply 0 retweets 0 likes -
Replying to @dakami
@dakami dnscrypt doesn't even send queries to root servers. It's clear you don't understand dnscrypt@jedisct1@taoeffect@davidu1 reply 0 retweets 0 likes -
Replying to @bitbbq
@bitbbq@jedisct1@taoeffect@davidu do you like end to end security semantics2 replies 0 retweets 0 likes -
Replying to @dakami
@bitbbq@jedisct1@taoeffect@davidu if dnscrypt is just point to point it's competing with dtls, not DNSSEC.3 replies 0 retweets 0 likes
@dakami @bitbbq @taoeffect @davidu You must be referring to dnscurve.
-
-
Replying to @jedisct1
@jedisct1@dakami@bitbbq@taoeffect That makes more sense...0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.