theres a legitimate problem here. https sites shouldn't get a "secure" or a lock. They should be the "normal" thing. Additional "Secure" in Chrome makes things worse. "Secure" should be the norm, have no indicator, only negative indicators for "not secure"https://info.phishlabs.com/blog/quarter-phishing-attacks-hosted-https-domains …
Yeah, I'm confused what you're saying here Hanno, isn't this already the plan? Are you saying you don't think the timeline is aggressive enough?
-
-
Chrome added an additional "Secure" recently, making the indicator stronger for the time being. While I know the long term plan is to get rid of that again I think that "Secure" is going in the wrong direction.
-
Don't like "secure" myself but willing to believe
@__apf__ and team's research trumps my gut feel.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.