3 ms·

All Chrome does when you visit an http site right now is put a subtle white warning icon and the words "Not Secure" next to the location bar, in lieu of the loc

All Chrome does when you visit an http site right now is put a subtle white warning icon and the words "Not Secure" next to the location bar, in lieu of the lock icon you get with https. There are no blocks, no big red scary icons, no password requests. The content on the page renders identically to a secure page. Technology moves on, and encryption is important, even if there are some cases where it's not strictly vital. Sure, some recipe page isn't a big deal, but there are plenty of sites out there that accept personal information and still have to be dragged kicking and screaming into the present to secure that information. Sadly the only thing that's going to solve that problem is forcing https-only at some point in the future.

reaperducer 6y ago
All Chrome does when you visit an http site right now is put a subtle white warning icon and the words "Not Secure" next to the location bar That's great. But Chrome isn't the only browser in the world. My point about browsers entirely blocking HTTP pages, putting up red scary icons and requiring a system password currently exists in Safari, both desktop and mobile. Technology moves on This is a lazy argument. And in my opinion, meaningless. encryption is important You are correct. But it is not required on every web site any more than everyone needs to carry a gun into a library to look up recipes.