Despite my best efforts at over-dramatization, and some inclination toward satire, I could not bring myself to title this post without any regard for accuracy. I did spin some sensationalist gems that I can’t resist sharing. I discarded these candidate titles due to their obvious discrepancy with reality:
- Kingdom of the Netherlands: Autonomy or subjugation for vassal states Bonaire, Saba and Saint Eustatius?
- Landscape of imperialism in the twenty-first century: Historically significant changes in sovereignty in the Netherlands Antilles.
Or most misleading and untruthful of all:
- Turmoil revisits Dutch West Indies half a millennium after rout of Spanish Armada!
Birth of Nations
In fact, the Netherlands Antilles ceased to exist as of October 2010. Curacao and Saint Maarten are now autonomous nations, governing themselves. The three islands Bonaire, Saba, and Saint Eustatius became municipalities in the Kingdom of the Netherlands. Residents now have the same benefits and rights as Dutch citizens.
While browsing the GeoNames site a few days ago, I first learned of the transformation of the Netherlands Antilles. It motivated today’s post, whose primary topic is privacy considerations for social networking. Location sharing (and associated geodata) is part of the privacy issue.
I was evaluating an alternative micro-blogging platform, identi.ca. It is a status.net project. identi.ca is like that mainstay of micro-blogging, Twitter. The two platforms even have a certain measure of cross-compatibility. In terms of branding, good choices were made: identi.ca is a partner, or possibly a subsidiary, of laconi.ca. laconi.ca is the perfect name for a communication medium restricted to 140 characters or less!
identi.ca is conceptually similar to the highly anticipated Facebook alternative, Diaspora. Both Diaspora and identi.ca are open source projects. For the user, the relevant issue is that both assure a higher level of privacy. The design model for Facebook, and many other social networking applications, is that very little information will be retained on the client side. Most everything goes to a server-side repository. It is irrelevant whether user data resides in the cloud, or the Facebook data center. Neither is under the control of the user.
identi.ca and Diaspora are different in that they do not require users to relinquish all personal data. One way to do this is by running one’s social network on one’s own server, thus avoiding the concerns of information misappropriation, be it intentional or accidental. Running one’s own server does not sound very feasible for most people, and in fact, the shift to client side is probably more subtle e.g. greater reliance on the user’s browser.
Google Buzz provides an example of accidental over-sharing. In the early days of Google Buzz, the full power of Open Social API was unleashed without forewarning users. This was accidental, and Google didn’t profit from the mishap. Google Buzz was irresponsible for not first offering opt-out to segregate some or all account contacts from participation. The issue was promptly remedied. Unfortunately, despite the rapid redress and that there was no revenue stream associated with the disclosure of information (unlike the copious chronology charts of Facebook’s information peddling showcased in the Wall Street Journal), Google’s temporary disclosure of information about users to each other had a very negative impact on acceptance, usage and success of Google Buzz.
Identi.ca includes a location identification option using GeoNames data. Tie-in to the Dutch West Indies follows: