This was a very good and timely story.<div><br></div><div>The message resonates load and clear and provides a decent framing of the challenges OpenID and its community and foundation have in front of itself:</div><div><br>
</div><div>* to frame the technology as a means to an end, and to more clearly depict what that end is and why it's good for people and the web </div><div>* to also articulate its benefits (if there are any) over technologies like Facebook Connect</div>
<div>* to articulate what the OpenID brand implies, how it should be used, in which contexts and what the trademark guidelines governing its use are</div><div>* to articulate a vision for OpenID in the marketplace, and what, if any, new market opportunities widespread deployment of OpenID would lead to</div>
<div>* describe how to deploy OpenID successfully; how to educate web users on why OpenID is beneficial to them and how to pick an OpenID provider; how to know whether a given site supports OpenID and whether they should link one of their existing accounts to the new site and what that means (i.e. sign in with OpenID)</div>
<div>* to improve OpenID for implementations in desktop and client software; how to make the overall OpenID experience more pleasant and natural</div><div>* to develop a narrative for the social web that pins OpenID at the center of the continued development of applications for the open web</div>
<div><br></div><div>As for comparisons between Facebook Connect and OpenID, while the outcomes of using either technology might be similar, or desirably similar, the fact that Facebook Connect relies on a single, central provider necessarily enables the kind of user experience that is simpler, is easier, is more grokable — so long as you're a user of Facebook. But the simplicity also removes choice, and the freedom to choose. And therefore we must fundamentally balance the complexity that stems from such freedom with the simplicity that comes from deciding what's best for the user, or the individual.</div>
<div><br></div><div>Chris<br><br><div class="gmail_quote">On Wed, Dec 3, 2008 at 1:55 PM, Alexandru Popescu ☀ <span dir="ltr"><<a href="mailto:the.mindstorm.mailinglist@gmail.com">the.mindstorm.mailinglist@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Don't we already have the Google and Yahoo! UX reports? Or is this<br>
article referring to something more than that?<br>
<br>
I haven't used yet the Facebook Connect login form, but I am really<br>
wondering if its simplicity is also addressing security concerns.<br>
<br>
./alex<br>
--<br>
.w( the_mindstorm )p.<br>
Alexandru Popescu<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
<br>
On Wed, Dec 3, 2008 at 1:29 AM, David Recordon <<a href="mailto:drecordon@sixapart.com">drecordon@sixapart.com</a>> wrote:<br>
><br>
> Memo to OpenID: Keep it simple, please<br>
> Webware.com 12/2/08 1:43 PM Caroline McCarthy<br>
><br>
> With all the buzz about Facebook Connect this week, it's worth asking the<br>
> question: Whatever happened to OpenID?<br>
><br>
> The universal login standard was created in 2005 by Brad Fitzpatrick,<br>
> founder of LiveJournal, while he was working at blog software company Six<br>
> Apart. (Fitzpatrick now works at Google; Six Apart has since sold<br>
> LiveJournal.) It has the support of Yahoo, MySpace (which just helped build<br>
> an OpenID extension for the Flock browser), and President-elect Barack<br>
> Obama's Change.gov. Even Google has dipped its proverbial toe in the pool.<br>
><br>
> But it wasn't until Facebook Connect started making headlines that the<br>
> concept of data portability--a single login across multiple sites--made the<br>
> jump from the tech press to the mainstream media. OpenID, some speculated,<br>
> had been left behind in the dust.<br>
><br>
> Hardly. But Wired's Michael Calore hit the nail on the head on Monday:<br>
> "Presenting a dialog that asks a user to log in to one website using a name<br>
> and password from another website is jarring, but Facebook has managed to<br>
> keep Facebook Connect simple enough for everyday users to understand. Such<br>
> ease of use virtually guarantees it will win support quickly."<br>
><br>
> The truth is, the future of the "social Web" is in expansion. And expansion<br>
> invariably involves dealing with a crowd beyond the Twittering,<br>
> FriendFeeding, WordPressing geeks who actually understand the concept behind<br>
> data portability.<br>
><br>
> And that's not made any easier by the fact that OpenID calls itself "an<br>
> open, decentralized, free framework for user-centric digital identity." Try<br>
> bringing that up in the boardroom of a non-tech company looking to ride the<br>
> social-networking wave. Then tell them that the most buzzed-about social<br>
> network on the planet will power your site's social features. The decision<br>
> will probably fall in the Facebook camp, unfortunately for the<br>
> open-standards crowd and its admirable dedication to all things balanced and<br>
> democratic.<br>
><br>
> "Nobody should own this. Nobody's planning on making any money from this,"<br>
> Fitzpatrick has said about OpenID. "The goal is to release every part of<br>
> this under the most liberal licenses possible, so there's no money or<br>
> licensing or registering required to play. It benefits the community as a<br>
> whole if something like this exists, and we're all a part of the community."<br>
><br>
> But your average company is probably going to care more about profit margins<br>
> than OpenID's decentralized ideal, and the possibility of having its user<br>
> activity broadcast across Facebook members' news feeds is tantalizing.<br>
> Especially during tough financial times, strategy will likely trump<br>
> idealism.<br>
><br>
> That said, there are some good signs for OpenID. It has a ton of support in<br>
> the tech world, and if Facebook Connect's impending expansion goes awry for<br>
> any reason--think Beacon--it could open up a whole new set of doors for<br>
> OpenID. What it (and other open Web standards) needs either way is some<br>
> image repair.<br>
><br>
> "Facebook is trying to replace all logins with their own, and control the<br>
> creation, distribution and application of the social graph using their<br>
> proprietary platform," Chris Saad, whose DataPortability Workgroup has put<br>
> its support behind OpenID and other open Web standards, wrote in a blog<br>
> post. "The most scary part of this, is that while Facebook is quietly and<br>
> methodically building out this vision with massive partners, the standards<br>
> community is busy squabbling about naming the open alternative."<br>
><br>
> OpenID and its brethren could use a good, simplified marketing pitch, not to<br>
> mention some announcements and partnerships that are more prominent than an<br>
> extension for a niche Web browser. They need to use the resources that the<br>
> likes of MySpace and Yahoo can provide to get more deals going and start<br>
> making headlines outside of ReadWriteWeb and TechCrunch.<br>
><br>
> And most importantly, in a recession, "it's good for the Web, so it's good<br>
> for everyone" just isn't concrete enough. One last tip for OpenID: Start<br>
> talking business benefits.<br>
><br>
</div></div>> _______________________________________________<br>
> general mailing list<br>
> <a href="mailto:general@openid.net">general@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
><br>
><br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Citizen-Participant &<br> Open Technology Advocate-at-Large<br><a href="http://factoryjoe.com">factoryjoe.com</a> # <a href="http://diso-project.org">diso-project.org</a><br>
<a href="http://citizenagency.com">citizenagency.com</a> # <a href="http://vidoop.com">vidoop.com</a><br>This email is: [ ] bloggable [X] ask first [ ] private<br>
</div>