Commentary

Michael Hickins
 

Facebook Punks Google With OpenID Adoption

Facebook's decision to adopt OpenID has been greeted with a lot of fanfare because of the notion that this is somehow a boon to users of social networks.

Facebook's decision to adopt OpenID has been greeted with a lot of fanfare because of the notion that this is somehow a boon to users of social networks.Nonsense. OpenID is a pain in the neck for users.

But it's a great deal for Facebook, which, while it enjoys a 200 million-strong following, is always on the hunt for more friends. Opening up to OpenID gives Facebook access to one of the largest populations of social networkers outside of MySpace (whom it shuns) and Twitter (whom it covets) -- and that's Google.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

By specifically naming Google, Facebook isn't even hiding its motivation for opening up to OpenID. In a blog posting announcing the move, Facebook developer Luke Shepard wrote:

Now, users can register for Facebook using their Gmail accounts. This is a quicker, more streamlined way for new users to register for the site, find their friends, and start exploring.
And a great way for Facebook to harvest the names of those people's friends from their Gmail accounts.

Shepard also wrote:

we've noticed that first-time users who register on the site with OpenID are more likely to become active Facebook users. They get up and running after registering even faster than before, find their friends easily, and quickly engage on the site.
All in all, a win-win for Facebook. For Google? Not so much. I don't see people signing up for Gmail accounts from their Facebook pages. Do you?

Not everyone agrees -- Marshall Kirkpatrick writes that this is "big news" because Facebook is the first big network that "allows users to log in with OpenID credentials granted to them by other companies' websites." And this is true. But it doesn't change the fact that Facebook will be the one that benefits the most.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links