3 ms·
Seems like a compromise on Google's part would be implementing something like: http://openid.google.com/username http://openid.google.com/username Standard URI
by gsiener 18y ago
Seems like a compromise on Google's part would be implementing something like:
http://openid.google.com/username http://openid.google.com/username
Standard URI, and would forward you to google to login as normal.
- axod 18y agoEnd users do not equate a URI as being anything that identifies them. To them, that is a website. Why is openID hell bent on trying to spin the tables on everything that people know and are used to? They know email address = my identification/username.
- michaelneale 18y agoyeah its confusing as all heck to users. The ONLY possible upside I can see, is that it slightly reduces the risk that they give the crown jewels (say, their Google User name and password) to some malicious site mistaking it for an open ID log in. In other words, the fact that the identity is the web site is a feature. It may not be the right feature, but I think there is some design thought behind it being a url. So users get used to not immediately providing a password, but instead this URL, and THEN after some redirect shenanigans, they do their password etc...