[OpenID] Google OpenID IDP is now live

[Eric Sachs]

>> Do you think there is going to be a rush of un-sophisticated Google
OpenID users at this point in time?  I might be mistaken, but Yahoo!, AOL,
myopenid are not whitelisting. What am I missing?
We just need to do the standard scaling, stability, translation quality,
etc. evaluation to make sure there are no major problems.  If we are lucky,
that won't take much time.  However it is more then likely that we will need
to tweak things in our user interface to make it easier to understand, and
unfortunately translating any such tweaks into 40+ languages takes awhile.

On Wed, Oct 29, 2008 at 2:18 PM, Dick Hardt <dick.hardt at gmail.com> wrote:

>
> On 29-Oct-08, at 11:36 AM, Eric Sachs wrote:
>
> >> I'd be interested in how Google thinks users will login with their
> OpenID if they can't type in gmail.com or google.com -- these should work.
> Will they?
>
> Since this is the first phase of our launch, we need to make sure it works
> stability (and with good usability feedback, including on validating the
> translation of our UI into 40+ languages) before we can claim that lots of
> RPs should use it.  Therefore there is currently a whitelist of supported
> RPs.
>
> If we published an XRDS file for gmail.com that worked automatically with
> existing RPs doing directed identity, then it would break for users because
> their RPs would not be on the whitelist.
>
> Once we are able to remove the whitelist, then we can post the XRDS file
> for gmail.com without breaking existing RPs who allow users to type domain
> names for directed identity.
>
>
> Ok. Now I understand why the XRDS is not there at this point.
>
> I don't understand why the RPs need to be whitelisted. Do you think there
> is going to be a rush of un-sophisticated Google OpenID users at this point
> in time?  I might be mistaken, but Yahoo!, AOL, myopenid are not
> whitelisting. What am I missing?
>
> -- Dick
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20081029/88591e12/attachment-0002.htm>