On Wed, Oct 29, 2008 at 2:48 PM, David Recordon <span dir="ltr"><<a href="mailto:drecordon@sixapart.com">drecordon@sixapart.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#FFFFFF"><div>Yeah, I think this general approach with the addition of knowing it is an email, doing directed identity, and passing the email as OpenID.identity is a good one. I really prefer to find a simple solution that doesn't involve running a mapping service or mucking with DNS.<br>
</div></div>
</blockquote></div><br>I agree with your sentiment, but treating "<a href="mailto:me@example.com">me@example.com</a>" as just "<a href="http://example.com">http://example.com</a>" in every instance precludes me ever using a different Identity Provider that is not "<a href="http://example.com">example.com</a>", assuming I like <a href="http://example.com">example.com</a>'s email service. <br>
<br>For example, <a href="mailto:david@yahoo.com">david@yahoo.com</a> will always be tied to using Yahoo.com as an OP. At least with a mapping service, Yahoo.com could offer it's users the ability to login with a Yahoo.com email address, but utilize a different company (e.g., <a href="http://myopenid.com">myopenid.com</a>) as their OpenID Provider (all configured from a Yahoo.com UI)<br>