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

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 t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Overcoming Imposter Syndrome

Imposter Syndrome is a cruel partner in your professional journey.  If you're not familiar with the term, it is essentially the feeling that you do not belong in a particular profession or that you do not deserve a specific role or set of responsibilities.  (You may read more in the Wikipedia article .)  I did not hear the term myself until I participated in a mentoring group for young employees at my current job - some of the young employees said they had this, and I won't deny a bit of surprise when I read what it is. If you feel this way, you're obviously not alone.  A good friend of mine suffers from this in no small amount in spite of the fact that she's an upper mid-level manager at her company with an organization of approximately 40 people reporting to her.  She feels this way because she never completed college, but fails to realize that her hard work and dedication to being the best that she can be is why she has been repeatedly promoted through the ra...