Conversation

Hey, remember when I said that #HTTP2's spec doesn't require TLS for it to be used, but de-facto it is necessary anyway because mainstream browsers like #Firefox and #Chrome will not support #HTTP/2 without #HTTPS?

Well I just realized now that thanks to #Mozilla and #Google's arbitrary limitations, they've actually made browsing the web with #I2P, #Tor (via onion/hidden services), and #Yggdrassil slower than it should be! The latency in Tor is so damn high that you essentially have to sacrifice speed if you're going to use an onion service that doesn't have an HTTPS certificate (which is unnecessary in the #encryption front because your connection to the onion is already encrypted!).

And I'm not even alone in this thought, look at this comment in bug 1418832 which never got a response from Mozilla.

Basically if you're a Tor hidden service operator, Firefox's devs are telling you to chalk up that $30 TLS certificate from harica.gr for the HTTP/2, and if you're operating a website over I2P or Yggdrasil, well "fuck your #privacy, get stuck in HTTP/1.1 lol"

I normally dunk on HTTP/2 (and personally I'm not even a fan of Tor) but this stupid decision by Mozilla as well as the equally stupid decision to drop HTTP/1.1 #pipelining means downstream (which Tor Browser is) will have to deal with this bullshit speed bump. HTTP/2's #multiplexing would've helped greatly in these average high latency situations!

This is why you never let politician-wannabes control your development