One of the more controversial predictions in my first book, Interface Culture, was that as software interfaces became increasingly cultural in nature -- closer to rock albums or novels -- interface avant-gardes would begin to form, tools for viewing information that were deliberately opposed to "mainstream" approaches, that challenged their users instead of talking down to them, sometimes to the point of being difficult just for the sake of it. (Like, say, giving your site a URL that was almost impossible to type properly.) I should have added the inevitable next stage in this process: the mixed feelings of regret, envy, and excitement among their followers when they sell out to the Man.
> I should have added the inevitable next stage
> in this process: the mixed feelings of
> regret, envy, and excitement among their
> followers when they sell out to the Man.
regret, envy, excitement...and maybe even panic. Imagine if Google sold its GMail product to another firm. I, for one, would be more than slightly nervous that I would lose access to the content of my email. But such mergers and acquisitions are to be expected. That is why the notion of "open and accessible content" is so powerful. This is what lets users effectively take their content with them. Downloading one's address book information into a CSV file is an example of this freedom.
I understand that this facet of application adoption is not that to which Interface Culture highlights in its identification of "avant-garde" data viewers. There is a relationship, however, between such views and open data standards: Open data standards engender the creation of different views of the same data. For Delicious, the primary data are the bookmarks, the corresponding user tags, and the relationships among the tags. Custom views include any of several Firefox plugins, and portlet-like Delicious webpage modules. A much more obvious custom view is that which is provided by any browser that is able to import a user's exported Delicious bookmarks. This last view is awesome in that Delicious provides the ability to perform this export. And this brings this (flailing) argument full circle by illustrating the worth of open data.
What is also illustrates is that the worth of Delicious is the service that it provides, and not the data that it stores. It's annoying that Yahoo!'s acquisition introduces much uncertainty into the future of this service. On the bright side, at least users can grab their data and start anew by building another custom view.
Posted by: Faiser | December 10, 2005 at 11:38 AM