No plan yet.
-
-
Tweet je nedostupan.
-
-
-
-
One question Emily: If the "not secure" warning only appears when *entering data* on HTTP and you don't see a positive signal eventually on HTTPS do they look the same then? How to know that an HTTP news site wasn't changed in the transport by an ISP?
-
The "not secure" grey warning will show for all HTTP pages starting in M68. So HTTP/HTTPS will never look the same. Does that make sense?
- Još 1 odgovor
Novi razgovor -
-
-
That's perfect! Thanks
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Remove the green locks and I'll never use chrome again!pic.twitter.com/Njh7MOwFYp
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Removing vital/useful features seems to be the new hot thing right now... I look at you
@gnome#zope4 and@googlechrome


-
Huh? No useful features are being removed here.
Kraj razgovora
Novi razgovor -
-
-
Will be great for the certificate fqdn mismatch to not be depicted as less secure than HTTP by the UI and messaging.
-
That ship sailed fifteen years ago, for good reasons.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

Moving towards secure-by-default indicators: we'll move towards removing "secure" indicators and marking HTTP as even scarier "not secure":