Hacker News new | ask | show | jobs
by TH3R3LL1K 2514 days ago
Chrome removed the green padlock as a way to show the its secured by default. Therefore, an error will show when it's not https. Could the author please explain why that is bad?
3 comments

I don’t use Chrome on iOS but Safari explicitly shows “Not Secure” for a non-HTTPS site. The secure ones have a padlock. My non-tech friends find this to be very clear; they have learned not to enter information when a website is “Not Secure”.

If this is the direction in which Chrome is heading, the 5-billion or so users will know, without a doubt, whether a site is secure or not. I don’t see a problem with this change, per se. The others, especially targeting ad blockers, seem to be a step in the wrong direction.

How would you know if they removed icon for non-safe sites. You wouldn't as there is no indication of that anywhere (no http string in address, no icon indication).

This brings unnecessary bit of burden to user who would have to pause to make sure site is safe (bank, etc).

That is a bit like trying to strip 'not occupied sign from public toilet stall. Claiming that if its occupied appropriate sign will be displayed.

Say you want to use a stall and you couldn't see a sign if its free or not, that will give u a small pause before you 'try' one.

Bump