<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 29-Oct-08, at 11:36 AM, Eric Sachs wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">>> <span class="Apple-style-span" style="border-collapse: collapse; ">I'd be interested in how Google thinks users will login with their OpenID if they can't type in <a href="http://gmail.com" target="_blank" style="color: rgb(119, 153, 187); ">gmail.com</a> or <a href="http://google.com" target="_blank" style="color: rgb(119, 153, 187); ">google.com</a> -- these should work. Will they?</span><br> <br><div>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.</div> <div><br></div><div>If we published an XRDS file for <a href="http://gmail.com">gmail.com</a> that worked automatically with existing RPs doing directed identity, then it would break for users because their RPs would not be on the whitelist.</div> <div><br></div><div>Once we are able to remove the whitelist, then we can post the XRDS file for <a href="http://gmail.com">gmail.com</a> without breaking existing RPs who allow users to type domain names for directed identity.</div> <div></div></blockquote></div><br><div>Ok. Now I understand why the XRDS is not there at this point.</div><div><br></div><div>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?</div><div><br></div><div>-- Dick</div></body></html>