Five Ways Facebook May Advance the OpenID Movement

This is a guest post by John McCrea, VP of Marketing at Plaxo. You can find John on his blog and his weekly video podcast on the opening up of the social web.

For the past two years, I’ve been a vocal advocate of OpenID and a big believer that OpenID and the rest of the “open stack” will bring about a Social Web characterized by interoperability, data portability, and user control. As a self-appointed evangelist for OpenID, I have often blogged on the topic or been quoted in articles covering the progress of OpenID. So when Facebook announced on Thursday that they were joining the OpenID Foundation, Justin reached out to me, asking if I’d like to do a guest post on how Facebook might contribute to OpenID. I was honored and eager to oblige, as I think this is truly a watershed moment for the industry. And so, here are five specific ways I believe that Facebook may advance the OpenID movement…

1) Continue to share insights from Facebook Connect. One of the highest priorities of the OpenID community is improving the user experience (based on the usability problems of early implementations). Facebook Connect is a great existence proof that third-party sign-on can be done in a way that is not confusing to mainstream users. Folks from Facebook came to the first OpenID User Experience (UX) Summit last Fall and were very open with how they developed and refined the UX for Facebook Connect, based on usability testing. And tomorrow, Facebook is hosting the follow-up to the UX summit, an “OpenID Design Workshop” at Facebook HQ in Palo Alto. Ongoing sharing of lessons learned from Facebook Connect will be invaluable to the OpenID community. This isn’t to say that OpenID should blindly adopt what Facebook has done, but blending the best of Connect with the distributed nature of OpenID is clearly a great idea.

2) Directly contribute to the evolution of OpenID spec. Beyond just sharing insights that others can translate into code, Facebook can directly contribute to the evolution of the OpenID specifications. Becoming a corporate member of the OpenID Foundation and naming Luke Shepard their representative sends a strong signal that they intend to do just that. As Mike Schroepfer says in the official blog post, “It is our hope that we can take the success of Facebook Connect and work together with the community to build easy-to-use, safe, open and secure distributed identity frameworks for use across the Web.” I believe Facebook is committed to helping OpenID realize its potential, and will be an active participant in the OpenID community’s open specification process going forward.

3) Become an OpenID “Provider”. Another great way for Facebook to contribute to the evolution of OpenID would be to launch an implementation of the spec ASAP. They can start by becoming an OpenID Provider, opening the door for a variety of experiments, like the one announced recently between Google and Plaxo, which is currently testing a “hybrid approach” to two-click signup that strings together OpenID, OAuth, and the Google Contacts API. Being an OpenID Provider would complement, rather than distract from Facebook Connect, which allows for more elegant and rich integrations with Facebook.

4) Re-write Facebook Connect atop the Open Stack. A great litmus test for OpenID and the other pieces of the Open Stack (OAuth, Portable Contacts, XRD, and OpenSocial), is whether a social network could use these open spec building blocks as a foundation for build something like Facebook Connect. Who better to do that, than Facebook? If Facebook embarked on that mission, it could very well offer the fastest path to progress. Working together, I believe we could see an Open Stack version of Facebook Connect by the end of the year. This aligns really well with Facebook’s vision to increase the “amount of sharing and openness” in the world, by advancing the technologies that, when widely deployed, will lower the cost of doing both.

Recommended articles