MySpace's Data Availability is not Data Portability

Yesterday MySpace, Yahoo!, eBay, Photobucket (also owned by News Corp), and Twitter announced the Data Availability Initiative. While I could write at length about how this shows the big companies have already realized how to diminish the DataPortability group’s brand by linking anything they do “data portability,” that isn’t the point of this post. The crux of the announcement yesterday was that shortly MySpace would begin allowing third-parties to embed MySpace profile information within their own services in the name of “data portability”. Unfortunately, the details around this remain buzzword-laden at best.

Their press release yesterday stated:

Additionally, rather than updating information across the Web (e.g. default photo, favorite movies or music) for each site where a user spends time, now a user can update their profile in one place and dynamically share that information with the other sites they care about. MySpace will be rolling out a centralized location within the site that allows users to manage how their content and data is made available to third party sites they have chosen to engage with.

At first glance this seems like a great thing. MySpace is partnering with Yahoo!, eBay, Photobucket, and Twitter to solve a pain point on the web; the inability to keep parts of your profile in sync around the web where you’d like them to be. The announcement didn’t however offer any insight into how this would work beyond that, “the MySpace Data Availability initiative uses OAUTH [sic] and Restful APIs as its core technology underpinnings.” After this announcement I had the pleasure of speaking with a reporter who was on the briefing call. He explained that MySpace said that due to their terms of service the participating sites (e.g. Twitter) would not be allowed to cache or store any of the profile information. In my mind this led to the Data Availability API being structured in one of two ways: 1) on each page load Twitter makes a request to MySpace fetching the protected profile information via OAuth to then display on their site or 2) Twitter includes JavaScript which the browser then uses to fill in the corresponding profile information when it renders the page. Either case is not an example of data portability no matter how you define the term!

To make this worse one of the pieces of profile information made available is a list of a MySpace user’s friends. Once again there are two reasonable ways to do this: 1) MySpace provides a user’s friends as a list of hashed email addresses to Twitter or 2) MySpace provides a user’s friends as a list of MySpace usernames. While the hashed email route would certainly be simpler and easier for sites like Twitter to match against their own user database, I highly doubt this will be the implementation due to concerns around undesired account linking. Rather I think MySpace will choose to provide a list of other MySpace usernames. What this means is that in order for Twitter to make use of the information they must encourage all of their users to fill in their MySpace account on Twitter so that they can map a MySpace username to a Twitter username. Obviously in the best interests of MySpace to have more of their profiles linked to from around the web thus increasing page rank, visitors, and thus ad revenue.

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.

Update: Just got off a plane from London and realized that I missed a link to Chris Saad, DataPortability’s co-founder, explaining yesterday that they “hope to see the MySpace “Data Availability” initiative evolve toward becoming a compliant implementation of the DataPortability Best Practices.” While MySpace did not say in their release that Data Availability is a form of data portability, it certainly seemed to be interpreted that way.

tags: , , , , , ,

Get the O’Reilly Data Newsletter

Stay informed. Receive weekly insight from industry insiders.

  • Couldn’t agree more David,and Facebook’s connect is equally as lame. Nothing more than extending the walled garden. Data portability means owning your info, not letting MySpace or Facebook own it for you.

  • Agree – this is not data portability – it is ‘data availability’.

    That’s why they described it as a first step, and joined the DataPortability project to take additional steps towards our best practices.

    As usual David, you have all the facts right but the conclusions are wrong.

    This does not diminish the brand of DataPortability – it shows clearly how the phrase and the project is accelerating the conversation and encouraging members to consult the community (in this case the community as represented by the DataPortability project) to ensure that long term, the implementations meet ‘best practices’.

  • Grendel

    Unfortunately DataPortability’s “Brand” is about all it has… A site wanting to implement the DataPortability “Spec” would be hard pressed to find the “There” there.

  • Project

    It might not be a popular opinion but in Facebooks case, Data Availability is far more important right now than Data Portability.

  • This IS data availability, sounds no good for me…

  • I think more than anything these developments are evidence of big boxes further reacting to market pressures. I think the tip of the long tail is far more powerful in this case than the big entities combined power:

  • Jimmymac

    Yes, there is a difference between Data Portability and the data availability that is now being pushed by MySpace, Facebook, and from what I hear, Google.

    The billion dollar question is, will everyday users see or care about the difference.

  • The regular user will not notice the difference between “data avalability” and “data portability”, the demo looks good, after all.

    The problem lies within the details of the TOS. MySpace (and Facebook for that matter) in effect owns your data (and the social graph), you are not allowed to export it at all.

    an excerpt from the TOS:
    “You will not, and will not permit any person, directly or indirectly, to […] distribute, sell, resell, lease, license, sublicense or transfer or otherwise make the Developer Platform or any User Information available to third parties (including by storing the Developer Platform or User Information in any manner which would enable a third party to access it (other than in the case of the User from which such User Information was retrieved (“Originating User”)). […]
    7.2.9 unless data is otherwise designated in writing by MySpace, you may not export any User Information and must cease using and delete any User Information or other MySpace Content within 24 hours after the time which you obtained such data;”

    the first part actually prohibits any displaying of the data at all (except to the user himself), because it is being made accessible to third parties.

    great stuff!

  • Flock 2.0’s integration with the MySpace Data Availability platform, which empowers users to take their social experiences across the web.