Update: Data Availability is not Data Portability or: Looking to BEATNIK
Just a quick round-up and update to yesterday’s post about the data hippie bandwagon: TechCrunch wrote a piece in which “data portability” is referred to as “The New Walled Garden” (strictly speaking, I guess the title should have read “data availability is the new walled garden”):
Internet giants know that the days of getting you to spend all of your time inside their walled gardens are over. So the next best thing is to at least maintain as much data about the user as possible, and make sure they identify with your brand while they are out there not being on your site. [...]
I think Facebook’s intentions aren’t to let users get data out of the network until Facebook is absolutely forced to do so, and then only on Facebook’s terms (see Facebook Connect). The fact is, this isn’t Facebook’s data. It’s my data. And if I give Google permission to do stuff with it, I’m damned well within my rights to do so. By blocking Google, Facebook has blocked ME. And that, frankly, kind of frustrates me. Let me put this another way. How dare Facebook tell ME that I cannot give Google access to this data!
David Recordon from O’Reilly also comes to the conclusion that “MySpace’s Data Availability is not Data Portability.”
At the end of the day it seems that MySpace is trying to become a large centralized profile repository on the internet. One where information might be available but certainly not allowed to be actually moved outside the network’s walls. A good try, but just as no one would like Microsoft own identity for the entire web with Passport I fail to see how others will let MySpace own all of the profiles.
How long until a social networking site comes up with TRULY user-maintained and user-owned, FOAF-based identity management tools, harnessing similar methods such as Henry Story’s BEATNIK semantic address book project?
Sphere: Related Content




May 16th, 2008 at 2:00 pm
I love playing with microformats, GRDDL, RDF etc. And while I find it a struggle to squeeze in my semantic markup fix in daily life, there are developers just sitting on bales of data that is just panting for it. It blows my mind that a developer managed to resist the urge to sneak in a hCard somewhere in Facebooks code, let alone FOAF.
May 16th, 2008 at 2:45 pm
Yes, you’d think that’d be a natural thing to happen – in particular because there are tons of people out there looking for the perfect start-up idea. Well, here is one! I wish _I_ were a developer…
May 22nd, 2008 at 3:29 pm
[...] Update: Data Availability is not Data Portability or: Looking to BEATNIK [via Zemanta] [...]
July 23rd, 2008 at 2:10 pm
[...] this restricted use policy? It seems as if, like before when MySpace signed up to data availability, they are first and foremost interested in “trying to become a large centralized profile [...]
July 28th, 2008 at 2:03 pm
[...] Update: Data Availability is not Data Portability or: Looking to BEATNIK [...]