Re:Google Goes Renegade, Creates Own OpenID Fork
by lux on Wednesday October 29, 2008 @07:27PM
(#348182)
For sure. This is a slight change, but a big change for the better. Nobody wants to remember a URL when they already remember their email. This makes perfect sense, and solves the biggest issue with OpenID in a way that looks like it puts it on par with the ease of use for end users of Facebook Connect, for example.
If every service simply required an email address, and the standard provided for a way to find out the access point from the OpenID provider, then we'd be all set and everyone would be able to implement this change.
Re:Google Goes Renegade, Creates Own OpenID Fork
by dsims on Thursday October 30, 2008 @02:40PM
(#348979)
Contact information should not be an identifier. It's like when a B&M store uses your phone number to ID you. I don't want them calling me and I don't want your website to email me.
The URL is simply a pointer to my identity, which is all I should have to give. The different formats the providers use is what makes it confusing (example.com, username.example.com, example.com/username, and now [email protected])
Users are comfortable using an e-mail address as an identity. Everyone has an e-mail address. This makes sense to end-users.
E-mail addresses are unique and they accurately identify who someone is. I have no idea why this wasn't the standard in the first place.