Hacker News Reader

All legacy content that is hosted using http protocol is, in fact, not secure. It's definitely not a bad thing to warn people.

View on HN

For general public 'not secure' imply something like 'not safe'.

That is exactly why Google's choice of wording is so poor. Far better would be 'encrypted/not encrypted' as that is all https really is. Safe can have far to many meanings and I won't be at all surprised when Google faces a class action when 'unsafe' things happen on a website they deem 'safe.'

Personally don't understand the heavy push to force https on everything and anything. The maintenance/time required to set up and maintain is not insignificant and is really quite pointless in many situations. Do you really need an encrypted connection to LOLCats?

You need an encrypted connection, period.

If you only use an encrypted connection when you need it, then one can know that, well, you need it.

You have nothing to hide... until you do.

Somebody better warn the Debian maintainers that their packages have been Not Secure for the past decade-or-more.

Reply on news.ycombinator.com