11–17 of 17 posts
I don’t think that in every case it is necessary down to user rejections. I can’t believe that in the netflix case users actually prefer to have to login with two post backs, one for the login, one for the password.
I don’t think that in every case it is necessary down to user rejections. I can’t believe that in the netflix case users actually prefer to have to login with two post backs, one for the login, one for the password.
This is a necessary pattern for increased security.
How are these leaked? Did someone hack into something?
I don’t think that in every case it is necessary down to user rejections. I can’t believe that in the netflix case users actually prefer to have to login with two post backs, one for the login, one for the password.
For example the buy now vs add to cart only on the Amazon one might have been looking at more than just how many products are sold, they might were also been trying to see if they can say reduce impulse buys that result in returns without lowering purchases that do not, in fact the reason they've kept the buy now might be because it actually reduced the return rate as people interacted less with the site and didn't buy additional items that they returned later.
In many of these cases, the "A/B test" may have been accidental. Running a software rollout is frequently done slowly, datacenter by datacenter, and during that time some people might see one version and others might see another. From the users perspective it looks the same as an A/B test, but the difference is nobody was looking at the results...
"Leaked..." How are these leaked? Did someone hack into something?
It could also be looking for possible A/B flags in cookies/localStorage.
Earlier quoted context omitted.
This is a necessary pattern for increased security.
What’s the security difference with two instead of one?
https://en.wikipedia.org/wiki/Secure_Remote_Password_protoco...