[PROPOSAL] Handle "http://user at example.com" Style Identifiers
David Fuelling
sappenin at gmail.com
Wed Nov 8 18:41:25 UTC 2006
I agree. In fact, given that most people don't know what an XRI is, we
might say there will be 3.5 times as much confusion.
;)
So, if in a hypothetical world where we have 4 potential OpenId "values"
that a user could enter, AND the goal is to reduce confusion, then does it
really make sense to cut out the most common "value" (which is an email
address)?
> -----Original Message-----
> From: Jonathan Daugherty [mailto:cygnus at janrain.com]
> Sent: Wednesday, November 08, 2006 1:30 PM
> To: David Fuelling
> Cc: specs at openid.net
> Subject: Re: [PROPOSAL] Handle "http://user@example.com" Style Identifiers
>
> # SIDE NOTE: For those who argue against email addresses in the OpenId
> # login form on the grounds of confusion, these 2 email proposals
> # should be no less "confusing" than trying to educate a user that the
> # Identity URL they type in (e.g., http://aol.com) is not their
> # identity. Both will/would take some education.
>
> Except that with this new feature, there would be twice as much
> confusion.
>
> And except that an openid works both as a normal URL and as an OpenID,
> whereas an email-like-thing may work as an OpenID, but is not always
> going to work as an email even though it looks like one.
>
> So maybe 2.5 times as much confusion. :)
>
> --
> Jonathan Daugherty
> JanRain, Inc.
More information about the specs
mailing list