And don't forget Twitter and Facebook's "Connect".<div><br></div><div>It would be nice if we established a convention and promoted it, but I'm not sure that'll happen.</div><div><br></div><div>Like profile photo sizes, each site does things a little differently and yet the effect of choosing any of the listed options doesn't really effect the overall usability of an app.</div>
<div><br></div><div>As well, "sign in" and "log in" no longer mean anything semantically — they're just short hand for "give me access to my account" (since "signing in" was something you did when you showed up for a field trip at school, and "logging in" was something you did on a black screen, green text terminal). </div>
<div><br></div><div>"Connect" is the more interesting language, since it implies an ongoing fusing of two resources — where data flows over a "connection"... not unlike what happens when you "plug in" a plug to a wall outlet. Until you sever the connection, the juice will flow.</div>
<div><br></div><div>I have also seen new language emerging in comment forms that is starting to approximate what it means to present an OpenID and confirm ownership of it:</div><div><br></div><div><a href="http://flic.kr/p/7eMb8H">http://flic.kr/p/7eMb8H</a></div>
<div><br></div><div>Here the language used it "identify yourself via"... </div><div><br></div><div>JS-Kit's Echo comment service uses the email metaphor to good, if not somewhat strange, effect:</div><div><br>
</div><div><a href="http://flic.kr/p/7fcHwU">http://flic.kr/p/7fcHwU</a></div><div><a href="http://js-kit.com/">http://js-kit.com/</a><br><div><br></div><div>Anyway, all this is to say that we haven't quite cracked the nut yet as to what's really going on with something like OpenID to say that "sign in" or "log in" is sufficient. "Connect" is closer, but obscures which data is being made available as part of that connection.</div>
<div><br></div><div>I'm glad you brought this up though, since it is something that bears inspection.</div><div><br></div><div>Chris</div><div><br><div class="gmail_quote">On Wed, Nov 11, 2009 at 8:27 PM, Johannes Ernst <span dir="ltr"><jernst+<a href="http://openid.net">openid.net</a>@<a href="http://netmesh.us">netmesh.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Informal Survey:<br>
<br>
Yahoo:<br>
Sign In<br>
<br>
Google:<br>
Sign in / Sign out<br>
<br>
Digg:<br>
Login / Logout<br>
<br>
Slashdot:<br>
Log In / Log Out<br>
<br>
AOL:<br>
Sign In<br>
<br>
MySpace:<br>
Log In<br>
<br>
Facebook:<br>
Login<br>
<br>
MSN:<br>
Sign in<br>
<br>
NYTimes:<br>
Log In<br>
<br>
<br>
... and this isn't even limited to OpenID Log/sign/in. Even capitalization and spacing is different.<br>
<br>
As part of the OpenID user experience, can we narrow this down? Or is that counter-productive?<br>
<br>
<br>
Cheers,<br>
<br>
<br>
<br>
Johannes.<br>
<br>
_______________________________________________<br>
user-experience mailing list<br>
<a href="mailto:user-experience@lists.openid.net">user-experience@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-user-experience" target="_blank">http://lists.openid.net/mailman/listinfo/openid-user-experience</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Open Web Advocate<br><br>Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><br>Follow me on Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a><br>
<br>Citizen Agency: <a href="http://citizenagency.com">http://citizenagency.com</a><br>Diso Project: <a href="http://diso-project.org">http://diso-project.org</a><br>OpenID Foundation: <a href="http://openid.net">http://openid.net</a><br>
<br>This email is: [ ] shareable [X] ask first [ ] private<br>
</div></div>