Group items tagged

The Echo Nest is a music technology company founded by two MIT Media Lab PhDs. The Echo Nest’s proprietary music analyzer API automatically analyzes audio (e.g., aif, wav, mp3, m4a), and generates an XML file describing the musical and structural content of the music. Computation takes about 1/50th of the duration of the track and the text output is about 1/20th of the size of its corresponding mp3.

Unlike other automatic methods of acoustic feature extraction, which progress strictly on raw audio signal, our technology was inspired by how people perceive music.  As a result, developers are able to automatically extract and use a wide array of time-based musical attributes for any song, including: timbre, pitch, rhythm, loudness, onsets, beats, tempo, sections, time signature, key, etc.

The social web is booming, signing up new users and generating new pieces of unique content at a steady clip. A recurring theme of the social web is "data portability," the ability to change providers without leaving behind accumulated contacts and content. Most nodes of the social web agree data portability is a good thing, but the exact process of authentication, authorization, and transport of a given user and his or her data is still up in the air. In this post I will take a deeper look at the current best practices of the social Web from the point of view of its major data hubs. We will take a detailed look at the right and wrong ways to request user data from social hubs large and small, and outline some action items for developers and business people interested in data portability and interoperability done right.

Basically what people are saying is that it’s a bad idea to give sites your usernames/passwords when you sign up. This creates a bad anti-pattern and sets a horrible precedent for users who simply give their email user/pass to hundreds of different startups with dismal security standards making it very easy for hackers to get to your sensitive data. It’s called the “password anti-pattern”.

In my mind Flickr provides probably the best page-flow pattern. So I’m saying the PROVIDERS are making this anti-pattern possible. Facebook must make it VERY easy to export users, so must Gmail and so must Yahoo etc. This must be standardized so that containers (using Open Social terminology) can provide that data using some kind of token system, and it must also happen in a process that doesn’t ask for you user/pass. I believe that because it’s not possible, networks are leaving developers with no other option but to do screen scraping.

Gartner analysts at the Gartner Symposium/ITxpo in Las Vegas discussed what they believe will be the most disruptive technologies through 2012. Disruptive technologies are those that force changes in industry models, business processes, vendor types, products and services, as well as the all-important user model. Take a look at this list and tell us whether you think something has been omitted—or just plain doesn't belong. This list is ranked in order from least disruptive to most disruptive.

What is needed though is a discussion about this and what the best practices in these cases should be. One option would be the opt-in for such XFN-markup but of course those links would still be available although not that easily extractable. Making it more private would probably harm the site’s usefulness. Removing them might also harm social services such as dopplr which make good use of them to find your contacts on dopplr.

So it’s many questions to be answered and I wonder what a good process might be to answer them. Surely there is the  around but of course they cannot just publish guidelines and the problem is solved. A broader discussion is needed and for a start maybe an exact description of the problem and coming from these some proposals to solve it.