Since you brought it up, Luke Shepard's recent post seems relevant:<div><br></div><div><a href="http://www.sociallipstick.com/2009/04/15/lets-detect-logged-in-state/">http://www.sociallipstick.com/2009/04/15/lets-detect-logged-in-state/</a></div>
<div><br></div><div>Chris<br><br><div class="gmail_quote">On Thu, Apr 16, 2009 at 5:15 PM, Ben Clemens <span dir="ltr"><<a href="mailto:bclemens@currentmedia.com">bclemens@currentmedia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">The nascar situation is akin to the difficulty in handling share (digg/facebook/email/myspace/buzz/etc/etc) options for content. Everyone has it on content pages, but it’s almost impossible to guess which subset of sharing sites you can show without overwhelming people (actually there is a hack to figure out which of them have been visited, but anyway...). Really all you can do is choose 3-5 of them that work well and provide a link for more. <br>
<br>
For choosing which identity providers, that means I’ll pick Google openid+oauth, Facebook, and Twitter to feature (and offer others secondarily). It’s unfair and leaves out major players, but at least I know those offer my users solid authentication and pass basic user attributes so I can make an account for them without a lot of trouble. Hopefully as people start to use these the most reliable, seamless experience will win and identity will settle around a few major players.<div class="im">
<br>
<br>
<br>
On 4/16/09 4:21 PM, "Chris Messina" <<a href="http://chris.messina@gmail.com" target="_blank">chris.messina@gmail.com</a>> wrote:<br>
<br>
</div></span></font><div class="im"><blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Just wanted to point out that Twitter is now offering sign-in with one's Twitter account using OAuth:<br>
<br>
<a href="http://apiwiki.twitter.com/Sign-in-with-Twitter" target="_blank">http://apiwiki.twitter.com/Sign-in-with-Twitter</a><br>
<br>
And, as if we didn't have enough buttons for the NASCAR [1], you can now use Twitter's button:<br>
<br>
<a href="http://twibs.com/oAuthButtons.php" target="_blank">http://twibs.com/oAuthButtons.php</a><br>
<br>
Oh, and it might interest some folks that there are interesting conversation going on about Twitter's authorization interface:<br>
<br>
<a href="http://groups.google.com/group/twitter-development-talk/browse_thread/thread/0a1739326384dac6?pli=1" target="_blank">http://groups.google.com/group/twitter-development-talk/browse_thread/thread/0a1739326384dac6?pli=1</a><br>
<br>
Chris<br>
<br>
[1] <a href="http://tr.im/fj_openid_nascar" target="_blank">http://tr.im/fj_openid_nascar</a><br>
</span></font></blockquote>
</div></div>
<br>_______________________________________________<br>
user-experience mailing list<br>
<a href="mailto:user-experience@openid.net">user-experience@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/user-experience" target="_blank">http://openid.net/mailman/listinfo/user-experience</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Citizen-Participant &<br> Open Web Advocate<br><br><a href="http://factoryjoe.com">factoryjoe.com</a> // <a href="http://diso-project.org">diso-project.org</a> // <a href="http://vidoop.com">vidoop.com</a><br>
This email is: [ ] bloggable [X] ask first [ ] private<br>
</div>