undefined | Better HN

story

0 pointsAnIdiotOnTheNet6y ago0 comments

> If you think of a standard user

You mean the strawman repeatedly trotted out by people defending shitty changes as justifications for why their shitty change is necessary? Ever wonder why so many things suck nowadays?

0 comments

zamadatix6y ago

Nope, just mean "not the guy that writes the webapp who needs to see if he is currently connected via HTTP or HTTPS".

Can "the larger group" be used as an excuse for a bad change? Sure! But so far the only reason mentioned as to WHY this change is bad is "www.site.com and site.com could technically be different sites" and I'm not sure how that is supposed to be clear regardless if www shows post load or not or how that's supposed to outweigh the advantages.

SAI_Peregrinus6y ago

> Nope, just mean "not the guy that writes the webapp who needs to see if he is currently connected via HTTP or HTTPS".

HTTP currently shows "Not secure" to the left of the URL. It's still easy to differentiate.

(I do think hiding www is stupid, but hiding http vs https is reasonable so long as they're still marked differently. Ideally http should be a more noticeable error, like it is if there's any user input box, or better yet a massive error like it is for self-signed certs and HTTPS.)

j / k navigate · click thread line to collapse