Well, I like it. =)
Well, I like it. =)
The problem we have with our project is that we're dealing with a ton of subdomains and not a lot of data I would consider "sensitive" enough to really necessitate encryption. While I appreciate the sentiment of the project, and value your commitment to privacy, for our use case it's definitely a bit of a pain in the butt.
That, and I know getting IT departments to move to install certs on their old infrastructure for things that might not require encryption is definitely painful. And the errors generated by expired certificates and "insecure content warnings" are confusing, and don't add value to projects that don't benefit from encrypted connections. We've been hearing all about it.
It's not important whether you consider the data sensitive enough to bother doing your job. It's actually your users, which, if they've installed HTTPS Everywhere, they do.
So get your shit together! :)
https://www.whitehouse.gov/blog/2015/06/08/https-everywhere-...