Re: Proposal: Marking HTTP As Non-Secure

Chris,

I'm a big fan of this rather progressive move from Google over the 
"Marking HTTP As Non-Secure".

1) Do you have any plans to make this feature enabled by default in 2016?
2) Do you have any plans to coordinate the change with other browsers; 
at least FireFox?

Thanks again.
- Jim

PS: Regarding "/There are no plans, at the moment, to add a No 
Skateboarding sign to Chrome/" what about the "no parking on bridge" sign?

On 1/29/16 3:02 PM, Chris Palmer wrote:
> On Fri, Jan 29, 2016 at 1:09 PM, <richard@leapbeyond.com 
> <mailto:richard@leapbeyond.com>> wrote:
>
>     You would be much better advised to create proactive mechanisms
>     for detecting suspicious activity (man-in-the-middle attacks) and
>     alerting when there really is a bonafide threat
>
>
> That is exactly what HTTPS is.
>
>     , as opposed to creating signal pollution in your UX.
>
>
>     I leave you with this:
>     http://image.shutterstock.com/z/stock-photo-street-intersection-congested-with-street-signs-57695734.jpg
>
>
> Currently, Chrome (and most other browsers) show only the equivalent 
> of the traffic light. We propose to wire up the red lamp. (Recently, 
> we unhooked the yellow lamp, precisely because a proliferation of 
> signals confuses and annoys people: 
> https://googleonlinesecurity.blogspot.com/2015/10/simplifying-page-security-icon-in-chrome.html)
>
> There are no plans, at the moment, to add a No Skateboarding sign to 
> Chrome.