Chrome 68 will mark all HTTP sites as “not secure”
The people who are pushing back against HTTPS really bug me to be honest.  They say silly things like “I don’t care if people see most of my web traffic like when I’m browsing memes.”<p>That presumes that the ONLY goal of HTTPS is to hide the information transferred.  However, you have to recognize the fact that you run JITed code from these sites.  And we have active examples of third parties (ISPs, WiFi providers) inject code into your web traffic.  When browsing the web with HTTP you are downloading remote code, JITing it, and running it on every site you visit if you aren’t 100% noscript with no HTTP exceptions.  You have no way of knowing where that code actually came from.<p>Now consider that things like Meltdown and Spectre have JavaScript PoCs.  How is this controversial?