How I recorded user behaviour on my competitor’s websites

Re:How I recorded user behaviour on my competitor’s websites by winkeltripel on Thursday August 23, 2018 @10:22AM (#17827471)

I mean, Google has been told (over and over) for a long time that HTTPS doesn't fix trust on the web being broken, and that the back button shouldn't have an API. These are both well documented security problems. What has happened now is that Google is under public pressure and scrutiny to actually fix these things. A fire has been lit under their bum, and rightly so.

[ Parent | on HN ]

Re:How I recorded user behaviour on my competitor’s websites by _bxg1 on Thursday August 23, 2018 @10:39AM (#17827629)

I believe they did remove the green lock from https sites to avoid implying trustworthiness. And removing the back button API is something Google can't decide on their own; it has to go through the standards process.

[ Parent | on HN ]

Re:How I recorded user behaviour on my competitor’s websites by hermitdev on Thursday August 23, 2018 @11:45AM (#17828206)

> I believe they did remove the green lock from https sites to avoid implying trustworthiness.

Nope. I'm on build 68.0.3440.106, the latest public stable build and as I'm writing this comment, little green lock and "Secure" right next to https://news.ycombinator.com.

[ Parent | on HN ]

Re:How I recorded user behaviour on my competitor’s websites by joshuamorton on Thursday August 23, 2018 @12:14PM (#17828465)

Its a process. The green lock will be eventually removed, and instead of the "LOCK Secure" you see now, you'll see nothing, and http-only sites will be "Unsecure". This you can already see if you go to a non-https site like neverssl.com. There's a "Not Secure" banner in white.

[ Parent | on HN ]