News for hackers. Stuff that matters.
Re:Google Goes Renegade, Creates Own OpenID Fork by zain on Wednesday October 29, 2008 @07:30PM (#348188)
If Google had stuck with the standard OpenID implementation, they could've still had the same user experience. http://[email protected]/ is a valid URL, and Google could've used that as the OpenID URL.
Re:Google Goes Renegade, Creates Own OpenID Fork by fallentimes on Wednesday October 29, 2008 @08:08PM (#348227)
Entering http before your email address doesn't make any sense to the average user.
Re:Google Goes Renegade, Creates Own OpenID Fork by Harkins on Wednesday October 29, 2008 @08:29PM (#348253)
Entering http doesn't make any sense to the average user.
Re:Google Goes Renegade, Creates Own OpenID Fork by fallentimes on Wednesday October 29, 2008 @10:05PM (#348329)
Exactly.
Re:Google Goes Renegade, Creates Own OpenID Fork by tlrobinson on Thursday October 30, 2008 @04:54AM (#348566)
The http:// is not necessarily required, he was just pointing out that it's a valid URI and thus can be used as an OpenID identifier.

It seems most OpenID implementations handle identifiers without the http:// prepended.

Re:Google Goes Renegade, Creates Own OpenID Fork by siculars on Thursday October 30, 2008 @12:37AM (#348437)
how hard would it be to slap "http://" onto the email if it wasnt there? that way you get your email and you dont break the standard. not hard, not hard at all.
Re:Google Goes Renegade, Creates Own OpenID Fork by tlrobinson on Thursday October 30, 2008 @04:52AM (#348563)
Most/all OpenID libraries already seem to handle identifiers without the http://

If the libraries don't already support the "@" syntax, they should.

If Google's way of doing things requires any proprietary changes, I'd say it's unacceptable, but if that's the only change necessary then it seems like a reasonable way of doing things.