Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Thomas Claburn

Thomas Claburn

Editor-at-Large

Google+ Name Policy Leaves Users Unsatisfied

Google tweaked its pseudonym rules after people complained--but some still-frustrated users say the company didn't listen well.

Having weathered considerable criticism for requiring that Google+ Profiles bear the name by which the user is commonly known, Google last week appeared to be warming to the idea of pseudonyms.

Bradley Horowitz, Google's VP of product, said "we've listened closely to community feedback on our names policy" and announced several features "that will address and remedy the majority of these issues."

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Google may have listened but its response has left many users doubting that the company actually heard them. Google introduced support for nicknames, names in non-Roman scripts, and established pseudonyms--those used by celebrities and well-known Internet figures.

Google+ users aren't buying it. "We are seeing a lot of rhetoric along the lines of 'we have learned' and 'our attitude is different now' but that has yet to translate into anything concrete which actually addresses (member) concerns about what sort of communities are possible on Google+," said Google+ user Simon Bridge in one of more than 400 comments posted in response to Horowitz's announcement.

[ Phishing may soon be much harder. Read Google, Microsoft Say DMARC Spec Stops Phishing. ]

If the statistics provided by Horowitz are accurate, then indeed the majority of name policy issues have been dealt with since 60% of name appeals submitted to Google--a majority--seek a nickname. Only 20% of name policy appellants want to use a pseudonym.

But if it is a minority that remains unsatisfied with Google's policy, it's a vocal minority. And among those Google+ users responding to Horowitz, the majority appears to believe that Google's changes are inadequate.

In the comment thread, Google+ chief architect Yonatan Zunger articulates the reason why Google's name policy is what it is: Google wants a name-based system rather than a handle-based system.

"This isn't a matter of functionality so much as of community: You get a different kind of community when people are known as 'Mary Smith' than when they are known as 'captaincrunch42,' and for a social product in particular we decided that the first kind of community is the one we want to build," he explained.

But supporters of pseudonyms, or nyms, dispute the claim that name-based communities are more civil than handle-based ones. Google's changes, they say, are not enough.

Free speech is not free from retaliation, in the U.S. or aboard, without at least a pseudonym for protection. When authoritarian governments favor real-name policies, the need for pseudonyms should be apparent.

If Google has grasped that idea, its hold on it seems tenuous. Google's acceptance of established pseudonyms appears to be so narrowly defined that only celebrities, or those famous enough to be impersonated, benefit from the policy shift.

Consider the case of Seebs.

Seebs wrote to InformationWeek complaining that nothing has really changed with regard to the way that Google handles pseudonyms. Seebs's legal name is "A Peter Seebach."

"No one calls me that," Seebs said in an email. "My spouse calls me 'Seebs.' My website is seebs.net." He has a Seebs email address and a Seebs Tumblr blog. His lawyer calls him "Seebs."

Google, however, won't accept that name for a Google+ Profile.

Seebs says Google's automated system requires more than one name. "The UI simply won't accept an attempt to enter a single name," he wrote. "(And yes, I know people whose legal names have only one component.) But if I enter my actual legal first and last name, "A Seebach", it requires me to submit an appeal--where in theory I can use the name I really use, "seebs."

As for the appeals process, Seebs says, "Basically, it's a joke. There is no provision for any commentary. At all. Submit documents or don't."

Seebs goes on to fault the appeals process as excessively automated--this is a longstanding complaint about Google's customer service in general, which isn't surprising given the absence of a Google Account fee to support a full-time call center for non-advertising customers. Google, he says, mistakes data for reality. "They are assuming that all real things have written documentation," he wrote. "...Google's Web crawl does not include what happens when I call my lawyer and his wife asks who's on the phone and he says "Seebs."

Seebs contends that Google's claim that it will recognize pseudonyms from people with an established online following just isn't true. "If you're not as famous as Lady Gaga, it doesn't count," he wrote.

In fact, Google does support some pseudonyms: Zunger acknowledges--rather remarkably--that Google will not attempt to verify fake names. "In fact, we do not give a damn whether the name posted is 'your' name or not: we will not challenge you on this basis, nor is there any mechanism for other users to cause you to be challenged for this," he said.

The problem Seebs faces is that Google+ requires an appeal for any mononym, a one-word name. However, Zunger suggests that the failure of Google+ to recognize mononyms may soon be resolved. Acknowledging that mononyms still trigger an automatic appeal, he says this is a known issue and it will be dealt with.

Horowitz in his post stresses that Google+ is still evolving. Yet, for a company that makes a fetish of speed, the evolution of Google+ isn't moving fast enough for those unable or unwilling to accept Google+ as a work-in-progress. Identity is fundamental, whether online or offline, and Google can't afford to offer only identity lite if it wants a happy, engaged community.

Social media are generating tons of data, but that data only becomes truly valuable when examined in context. Attend the virtual Enterprise 2.0 event Social Analytics: The Bridge To Business Value, and learn how social analytics will provide the bridge to unlocking business value. It happens Feb. 16.



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

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE 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. BYTE 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.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.