content: It kind of seems like a good idea on the surface. Security is a good idea, who'd be against more security in all places, all of the time? But consider this counterpoint. If you have a website that doesn't deal with user input or sensitive information (logging in, payment details, etc) you don't necessarily need an HTTPS connection. What's the point for a typical blog where you want to post a few articles or display some of your artwork for example? Now a typical person who wants to create a website has to worry about secure connections, and maybe shelling out non-trivial money for an SSL certificate. There's also more places where you have to signup and register (to get the SSL certificate) so there's more places for governments to get personal details and create barriers and problems for people. So now there's one more barrier for entry that discourages people from creating blogs, and more people will just say "fuck it" and rely on all off the walled gardens like Facebook/Twitter/Tumblr/etc for posting content where all public thought can easily be monitored and controlled. I don't necessarily think that's healthy for the open web. I understand that it's hard for normal people to contextually grasp when a secure website might be needed and when it's not needed so it might be just easier to push this idea of "all websites need to be secure all of the time" but really they don't.