The Boy Who Cried “Privacy Breach!”

Wolf wolf wolf

This was originally published in MediaPost's Social Media Insider, and I was originally going to call it "Privacy, Shmivacy" but deferred to Aesop instead. Image source: knowyourapps.com.

The Boy Who Cried "Privacy Breach!"

Gather around for a story, boys and girls. Stop me if you've heard this one before.

Once upon a time, there was a boy tending his social flocks of friends and followers. He would continually go up to the social embankments and shout, "Help, there's a privacy breach!" The bloggers and reporters would all come running, making his cries travel much further. Masses of people changed their privacy settings, even though their privacy wasn't violated at all. Then one day, there really was a serious privacy breach, but when the bloggers and reporters and tweeters and plussers and tumblrers all came along to convey the cries out unto the world, no one believed it was a big deal. The evil privacy breacher then stole all their identities, sold them to a Moldovan spam syndicate, and last was seen in Dubai skiing in an indoor mall.

Aesop it's not; the version at mythfolklore.net reads better. Yet this story is painfully relevant today. In the past week, there have been two such baseless privacy scares involving LinkedIn and Facebook, and they're unfortunate red herrings.

Let's start with LinkedIn.

The "privacy breach": LinkedIn was preparing a new form of social advertising. It said, "When LinkedIn members recommend people and services, follow companies, or take other actions, their name/photo may show up in related ads shown to you."

The gotcha moment: Steve Woodruff, a blogger friend whom I've known and respected for years, got a tip about it and blogged the story. He wrote, "Devious. And I expect that you, like me, don't want to participate."

Why it's not a big deal: LinkedIn did something unprecedented by allowing an opt-out mechanism before anyone saw an ad using that kind of targeting. Yes, the default was LinkedIn opting people in, and LinkedIn could have communicated these changes better (though it did start disclosing the changes as early as June), but in many ways LinkedIn was well ahead of the curve.

The upshot: LinkedIn caved, and will be worse off for it. Instead of LinkedIn showing you that your friends Ashmi, Jamison, and Lexi like an advertiser or its products, you'll just see that three nameless friends follow that company. Look at the before and after images in LinkedIn's mea culpa. Which looks better? The bottom one is McMurphy at the end of "One Flew Over the Cuckoo's Nest." It's a loss for LinkedIn, and I hope they find a way to keep experimenting with social ads, while leading the way with privacy.

Then there's Facebook.

The "privacy breach": People using Facebook's mobile applications were startled to find that friends' phone numbers were visible in their contact lists at facebook.com.

The gotcha moment: There are too many instances of yellow journalism to name, but the normally sound Boy Genius Report ran one of the scarier headlines: "Facebook stole every contact and phone number in your phone – here's how to undo the damage." The post then notes that you'll express "shock and disgust."

Why it's not a big deal: This is an old feature from Facebook so you can add friends based on their phone numbers, and it's very useful. You can disable contact syncing if you want — that's an old feature too. As Facebook noted in its response, "Just like on your phone, only you can see these numbers." Umm, what damage is this? When you synchronized your Hotmail and Gmail accounts with Facebook to find friends there, Facebook didn't email everyone else. Similarly, Facebook's not going to start calling your grandmother and reading her your status updates. That would be a great service, though, as I should call Grandmom more anyway, and Mark Zuckerberg sounds enough like me.

The upshot: Unlike LinkedIn, Facebook didn't make any changes. There are probably a lot of features in Facebook's mobile apps that you don't know about, and there are probably a lot of privacy settings you don't know about either.

You may recall that the original boy who cried, "Wolf!" lost his flock of sheep. The dangers are far worse for those who make a big stink of nonexistent privacy breaches. When we make a fuss over what are at most minor communication snafus from the social networks in question, we won't be able to rouse people's attention when serious issues emerge.

Few people truly understand privacy issues. Your personal information on your cheap, plastic supermarket loyalty card is currently worth far more than all your social graph data. That's right — how much toilet paper you buy is far more valuable to marketers than who your friends are. If bloggers investigated shopper cards, they'd tell you to cut them up, and then for good measure to never step foot in a supermarket again.

There are lots of morals to this story: Don't jump to conclusions. Do your homework. Count to 10 before writing a blog post. Don't be the boy or girl who cries, "Privacy breach!" And always remember to call your grandmother.

2 thoughts on “The Boy Who Cried “Privacy Breach!”

  1. I really agree with the facts that you have shared on this post. An interesting topic like this really enhances reader’s mind to have more effective decisions over a certain issue.
    bodrum tatilköyleri

  2. I really agree with the facts that you have shared on this post. An interesting topic like this really enhances reader’s mind to have more effective decisions over a certain issue.

Comments are closed.