[PROPOSAL] Handle "http://user at example.com" Style Identifiers
George Fletcher
gffletch at aol.com
Fri Oct 20 18:43:44 UTC 2006
It might create some confusion depending on the audience. For the
audience that doesn't run their own web server, or have their own blog,
it might be confusing to enter a URI.
This approach would help those users make the transition without
restricting the users who do "get it" from entering URIs. It also
provides a simple way for RPs to appeal to a larger set of users (e.g.
my mother-in-law wouldn't understand what to enter if asked for a URI
based identifier).
Thanks,
George
P.S. Hopefully I've got Thunderbird sending plain text messages now so
they don't get "scrubbed" in the archives. Sorry about that.
Recordon, David wrote:
> Yes, potentially. It is a bit of a hybrid approach I guess.
>
> --David
>
> -----Original Message-----
> From: Jonathan Daugherty [mailto:cygnus at janrain.com]
> Sent: Friday, October 20, 2006 12:59 PM
> To: Recordon, David
> Cc: Drummond Reed; specs at openid.net
> Subject: Re: [PROPOSAL] Handle "http://user@example.com" Style
> Identifiers
>
> # The thing is they aren't really giving them their email address.
> # Rather an identifier which looks like an email address to a user and #
> in some cases may also be an email address.
>
> Isn't that likely to create a lot of confusion?
>
> --
> Jonathan Daugherty
> JanRain, Inc.
>
> _______________________________________________
> specs mailing list
> specs at openid.net
> http://openid.net/mailman/listinfo/specs
>
>
More information about the specs
mailing list