• Blog
  • Talks and Presentations
  • Whitepapers and more
  • In The News
  • About Talking Identity
  • About Me

Google+ and The Trouble With Tribbles

  • Posted on:September 1, 2011
  • Posted in:Personal Identity Management
  • Posted by:Nishant Kaushik
2

pseudonymityIn a prior post I talked about the backlash against the “Real Names” policy that Google has instituted for it’s Google+ social network. The resulting nymwars are in full force, and drew me into a very interesting twitter back-and-forth between Kevin Marks, myself and Tim O’Reilly over the weekend, which Kaliya (or IdentityWoman, as she is really known) documented here. Today, it prompted Gartner’s Distinguished Analyst (and Prophet of Pull) Bob Blakley to fire a salvo at Google’s “insanity” in creating “an antisocial space in what is supposed to be a social network (that) is at odds with basic human social behavior”. It’s an excellent post in inimitable Bob style, but I did want to focus on one point where I may differ from Bob a bit.

In his post, Bob talks of Google trying to do social with an eye on the lucrative targeted advertising dollars that Facebook is currently hogging. This is the motive I alluded to at the end of my post as well. But things (appear to) have become a bit clearer here (albeit still speculation). During an interview with NPRs Andy Carvin, Google CEO Eric Schmidt didn’t throw out the usual pro RealName arguments about maintaining civil discourse online and such, but basically talked about Google’s ambition to be an identity service – a platform on which commerce and government services can run. And for such a platform to be widely adopted and billable, the data needs to have a certain fidelity – no different than the kind of identity stores we build within enterprises today.

Google already has such an identity platform – it’s called Google Profiles. If you’ve ever created a GMail account for any reason – as a GMail user, to enable an Android phone, for using Picasa – you have a Google Profile. The problem is that these service-derived profiles are of low value to the user, created only to get on to the desired service, and so they are never maintained and have low data quality. And like in a lot of enterprises that engage in identity administration and provisioning projects, Google has to deal with multiple identities per person that need to be linked and correlated. If doing that is hard in the enterprise space, imagine how hard that is do in the personal space where users not only have no reason to facilitate this, they actively engage in keeping some of these profiles separate and distinct. Just in writing this post I noticed that mine still reflects my Oracle position – unlike my LinkedIn, Twitter and Facebook profiles. The common thread through those three services that I kept up-to-date? They’re social, an extension of me into the online world.

That’s why Google+ is so important to Google’s aspirations for Google Profiles. Google wants to use social as the honeypot that draws in all those users and keeps them highly engaged and motivated to keep their data up-to-date. They see how well this is working for the Facebook identity platform and want to replicate that success. But here’s the disconnect – Facebook got to this spot organically. While Zuckerberg may be a visionary in many aspects, his first priority when building Facebook was to build a social network where people would hang out. As the social engagement increased the number and fidelity of identities in Facebook’s database grew as well, The team then pounced on the opportunity to build a platform out of this. In true engineering-driven style, Google is reverse engineering this – seeing where they want to get to and trying to replicate the same path, but instituting fixes that short circuit what took Facebook years to do. Except that there are no shortcuts.

The trouble with social is that it is social – with all the norms, behaviors and expectations that come with that. You cannot re-engineer that overnight (Facebook is being far more successful in doing so using far more insidious means). Facebook also has a policy of Real Names, but it realizes that to make the social work you have to cater to the psychology of the users. So there are no identity verification processes, no automatic suspension of accounts and schemes that entice us to provide real data instead of telling us to do so. The fidelity of the data is proven by it’s socially verified reputation, not because there is a policy document that can be pointed to (at the end of the day, a much more robust and legitimate mechanism).

Do you know what you get if you feed a tribble too much?

Do you know what you get if you feed a tribble too much?

Google may think that social is all cute and cuddly, but they may be about to find out that it’s a completely different beast that could clog up their systems. Meanwhile, the battle for our online self-determination will continue. IIW XIII should be a lot of fun.

Be Sociable, Share!

  • Tweet

Tags: Digital IdentityFacebookGoogle PlusGoogle ProfilesGoogle+Identity ServicesIIWNymWarsPrivacyPseudonymityReal NamesRealName
  • Pingback: Google+ Can Be A Social Network Or The Name Police – Not Both()

  • http://www.pekanbaru.co/ Pekanbaru

    this is all strictly business and competition. but behind that google should really serious tocompete and offer better terms than its competitors…

Recent Posts

Securing Our Biometrics-Based Future
The last few years have seen an uptick in efforts to use biometr...
My Next Gig: Delivering the Identity-Defined Perimeter with Uniken
Back in 2013, I opened my 'Hitchhikers Guide to Identity' talk w...
Invisible Identity, or How to Delight People & Secure Users
So I waited patiently for the folks at the Cloud Identity Summit...
Doing 2FA Better Could Mean Using Social Factors
In my last post regarding weaknesses in how 2FA is implemented i...
Doing 2FA Correctly Requires More Than 2 Factors
Two Factor Authentication (or 2FA) has been in the news a lo...

Recent Comments

Talking Identity | Nishant Kaushik's Look at the World of Identity ManagementHow Not To Enhance Your Customers Security - Talking Identity | Nishant Kaushik's Look at the World of Identity Management on
The Epic Hacking of Mat Honan and Our Identity Challenge
112 weeks ago

Talking Identity | Nishant Kaushik's Look at the World of Identity ManagementHow Not To Enhance Your Customers Security - Talking Identity | Nishant Kaushik's Look at the World of Identity Management on
#FAIL No More: The Rise of the Self Defending Enterprise
112 weeks ago

NishantKaushik on
That Time Enabling Two-Factor Authentication Made Me Feel Worse
114 weeks ago

Gabor Szathmari on
That Time Enabling Two-Factor Authentication Made Me Feel Worse
114 weeks ago

UK Access Management Focus · Reputation is everything on
The new Identity Equation
127 weeks ago

Connect

Twitter Follow @NishantK

LinkedIn Connect on LinkedIn

Vimeo View Nishant's Talks

About Me nishantkaushik.com

Categories

  • Ask Dr. K (12)
  • Identity Services (36)
  • Identropy IDaaS (4)
  • Insight IdM (149)
  • Oracle Identity Management (61)
  • Personal Identity Management (33)
  • The Cloud Identity Series (24)
  • Tips & Techniques (4)
  • User-Centric Identity (24)

Archives

  • ► 2018 (1)
    • January 2018 (1)
  • ► 2017 (1)
    • April 2017 (1)
  • ► 2016 (9)
    • December 2016 (1)
    • October 2016 (1)
    • August 2016 (1)
    • June 2016 (4)
    • February 2016 (2)
  • ► 2015 (5)
    • November 2015 (1)
    • June 2015 (2)
    • April 2015 (1)
    • February 2015 (1)
  • ► 2014 (8)
    • October 2014 (1)
    • September 2014 (2)
    • August 2014 (1)
    • July 2014 (1)
    • June 2014 (1)
    • February 2014 (2)
  • ► 2013 (12)
    • December 2013 (1)
    • August 2013 (2)
    • July 2013 (5)
    • June 2013 (1)
    • April 2013 (1)
    • February 2013 (1)
    • January 2013 (1)
  • ► 2012 (13)
    • November 2012 (2)
    • August 2012 (3)
    • July 2012 (2)
    • June 2012 (2)
    • May 2012 (1)
    • February 2012 (3)
  • ► 2011 (29)
    • December 2011 (1)
    • November 2011 (1)
    • October 2011 (1)
    • September 2011 (2)
    • August 2011 (3)
    • July 2011 (4)
    • June 2011 (5)
    • May 2011 (3)
    • April 2011 (4)
    • February 2011 (2)
    • January 2011 (3)
  • ► 2010 (33)
    • December 2010 (1)
    • October 2010 (1)
    • September 2010 (4)
    • August 2010 (5)
    • July 2010 (6)
    • June 2010 (4)
    • May 2010 (3)
    • April 2010 (2)
    • March 2010 (3)
    • February 2010 (2)
    • January 2010 (2)
  • ► 2009 (24)
    • December 2009 (1)
    • November 2009 (1)
    • October 2009 (3)
    • September 2009 (3)
    • August 2009 (4)
    • July 2009 (2)
    • June 2009 (2)
    • May 2009 (3)
    • April 2009 (1)
    • February 2009 (2)
    • January 2009 (2)
  • ► 2008 (44)
    • December 2008 (1)
    • October 2008 (4)
    • September 2008 (4)
    • August 2008 (8)
    • July 2008 (11)
    • June 2008 (4)
    • May 2008 (2)
    • April 2008 (2)
    • March 2008 (3)
    • February 2008 (3)
    • January 2008 (2)
  • ► 2007 (56)
    • December 2007 (3)
    • November 2007 (5)
    • October 2007 (6)
    • September 2007 (5)
    • August 2007 (8)
    • July 2007 (5)
    • June 2007 (9)
    • May 2007 (3)
    • April 2007 (2)
    • March 2007 (5)
    • February 2007 (5)
  • ► 2006 (33)
    • December 2006 (4)
    • November 2006 (2)
    • October 2006 (6)
    • September 2006 (1)
    • August 2006 (2)
    • July 2006 (3)
    • June 2006 (5)
    • May 2006 (3)
    • April 2006 (2)
    • March 2006 (5)

Disclaimer

Talking Identity is my exploration of the world of Identity Management. The views expressed on this blog are my own and do not necessarily reflect the views of my employer (doesn't mean I'm not trying hard to mold them in my own image).

Copyright © 2005-2013 Nishant Kaushik. All Rights Reserved.