> Same with https errors… That's a branding issue: we've been selling "https://" https://" as secure, so we can't go back now and reeducate users. We should ha

> Same with https errors… That's a branding issue: we've been selling "https://" https://" as secure, so we can't go back now and reeducate users. We should have decoupled the idea of security from the protocol used (https can be insecure) and used a separate channel entirely to communicate security, e.g. what browsers are doing now with padlocks or colour schemes. But it's too late to change the SSL UX.