Skip to main content

The Price of Privacy

Here's an update on my job situation as a follow-up to my blog entry last week. I found another position within the same company in a role that fits me better by an order or magnitude. To make it better, I received a payraise too.

Being proactive gets you noticed. In fact, it was remarked that my attitude demonstrated that I already had the qualities that my new boss was seeking in the successful candidate.




Privacy has a price. Don't believe me? Ask Facebook. Before I explain that, though, let's have a history lesson.

Facebook started as a joke of sorts. According to Wikipedia (which, in turn, got this information from a 2008 Rolling Stone article), Mark Zucker wrote its predecessor as a Harvard version of HotOrNot to take his mind off of a girl that had dumped him. This evolved into a means for college students to link up in order to stay in touch. Finally, it became the behemoth that we know (and love?) today.

The problem started when Facebook realized that it had a substantial user base.* When you have over 100 million users and all of their associated data, you start to wonder if there is any way to make money off of this. Granted, Facebook started receiving venture capital less than 6 months after work was started on the site in January 2004. But venture capital is one thing - the big payoff (and the reason for the VC investment in the first place) is something else entirely.

* This is speculation, of course, but I daresay it isn't far from the truth.

The first inklings of this desire to make beaucoup bucks reared their ugly heads in November 2007 with the Beacon project. Since the media uproar and subsequent public outrage that followed, Facebook has constantly been in the spotlight (often for poor reasons rather than positive ones) due to its ever changing privacy policy. While the true reasons for the constant changes to the privacy settings, etc. may never be known, it isn't too hard to speculate that Zucker et al are continuing to strike business deals with other websites where they exchange demographic and preference data in exchange for cold, hard cash.

Now a new wind is blowing, however. While social networks aren't new (c.f. Jive Software, Intralinks, Wellness Layers, etc. which all make some form of enterprise-class social networking / collaboration software), the popularity of Facebook in spite of its "mayhem and nonsense" has made it the only social network site worth considering...until now. Recently, the media has been raving about four NYU students who have decided to create an open source Facebook competitor (named Diaspora). Why have they decided to do this? They, like many of the rest of us, got fed up with the lack of control over how our data from Facebook is used, and they want to do something about it. In fact, in the few short months since they announced their intention, they have already raised USD$115,000 in "crowdsourced" funding (i.e. not coming specifically from angel investors).

Again, their idea isn't new. There are other alternatives already under development (OneSocialWeb, for instance). But what they are doing highlights the issue of privacy at Facebook. After all, who wants to stand up and make the claim that their privacy policy is longer than the American Constitution?

In all seriousness, I don't see how Facebook can win this battle. If you keep quiet about it (like they did with Beacon), someone will eventually find out and roast you alive. If you tell people about unexpected use of social data (like Google recently did when they said they inadvertently collected data from unsecured WiFi networks while their streetcam cars were roaming the streets) then the world will start by expressing concern (or by outright blasting you to bits) over the disposition of the data and end by...well...comparing you to Facebook. All in all, I would claim that the latter scenario is preferred since Google at least has some credibility and will successfully defend itself on the strength of the word "inadvertently."

Still, it's only due to its existing reputation that Google will ultimately escape unscathed. Facebook can only wish that it enjoyed this luxury.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ