Posts Tagged blip
Jason has put together a mashup (ah, that term seems so old and dated now) that combines twitter, blip.fm, and the Echo Nest. When you Blip a song, just add the tag #recsplease to the twitter blip and you’ll get a reply with some artists that you might like to listen to.
This is similar to recomme developed by Adam Lindsay but recomme has been down for a few weeks, so clearly there was a twitter-music-recommendation gap that needed to be filled.
Check out Jason’s Blip.fm/twitter recommender bot.
The fine folks over at Grooveshark have just released Twisten.fm. Like Blip.fm, Twisten.fm combines micro-blogging and music, and like Blip.fm, instead of creating an entirely new microblogging network, Twisten.fm piggybacks on top of the existing Twitter network.
With twisten, you can make tweets with just about any song in the world (Grooveshark has millions of tracks in its catalog) – twisten will automatically generate a twisten tiny url to the song, and if any of your twitter followers click on the link, they are taken directly to the song page on Grooveshark where they can listen to the song.
Here’s what the song tweet looks like on twitter:
Twisten makes it easy for you to tell your twitter followers that you like a song – with Twisten, you just type the name of the song, and twisten does all of the hard work of finding the song in the catalog, generating a tiny URL for the song and posting it to Twitter.
Twisten also makes it easy to listen to music posted by others. If you use the Twisten web app, you can easily listen and browse all of the twisten tweets of your followees or the world at large.
With the twisten app, you just see the Twisten tweets, which makes it a perfect app for browsing through new music. It is easy to listen, since the player is embedded right in the page. You can also listen to the music that is being posted by everyone.
I suspect that Twisten.fm is going to be a really big deal. First and foremost, it is an incredibly viral app. Just by using Twisten, you are telling all the world about it. 18 hours after it’s release, Twisten is #6 on the list of Twitter trending topics.
Second, it doesn’t re-invent the wheel. Instead of building a whole new social network, it sits on top of Twitter, one of the largest existing social networks – it doesn’t have to build up a network from scratch.
Twisten is really neat, I like it a lot – still, there are a few places where it could be improved.
First of all, when listening to music on the Twisten site, the music should never stop when I navigate to a different part of the site. Right now, if I’m listening to a particular tweet, and decide to check out what ‘everybody is listening to’, the music stops. The main Grooveshark app does a much better job of keeping the music playing all the time whilst one navigates through the site.
Currently, when I click on a twisten tiny url in twitter to listen to a song, instead of taking me to Twisten, the URL takes me to Grooveshark. I understand that Grooveshark is hosting all of the music, but it seems to me that if you want to really make Twisten go viral, the links should bring listeners straight to Twisten, where they can listen to the music, and while there, start Twisten their own tweets.
The listening experience on Twisten is a hunt-and-peck style. I see a song, I click on it, I listening to it, and then I go and find the next song. That’s fine when I am exploring for new music, but if I just want to listen to music, I’d like to be able to turn Twisten into a radio station, where I listen to the music that my friends have been twittering. Ideally, I should be able to listen to tweets all day without having to click a mouse button. TheSixtyOne does a great job of keeping the music flowing. Twisten should follow their model.
I wish Twisten.fm would scrobble all my tweets and listens – it’d be great if every music app in the world scrobbled my listening behavior.
Twisten is able to collect all sorts of interesting information about who is listening to what music. I hope they do some interesting things with this data. For instance, they could create a Twitter Music Zeitgest that shows the songs and artists that are rising, popular, or falling. Since Twisten knows what I’ve been listening to, and what I like (because I can ‘favorite’ twisten songs), Twisten should be able to connect me up with other Twisten listeners that have similar tastes so I can use their twitters and listens to guide my own listening. Twisten is going to be able to collect lots and lots of user listener data, so it should be interesting to see what they do with it all.
Twisten has the potential to be the real breakout music application of 2009. It has all the ingredients – a huge catalog of free music, and a viral model that leverages one of the largest and most active social networks. When iLike released it’s facebook app, iLike became the fastest growing music app ever, adding 3 million users in two weeks. Twisten has a good chance to do the same thing.
Blip.fm is often described as a twitter for music. Blip users post ‘blips’ to tracks – and as with Twitter, others can follow your Blips and listen to what you’ve posted. It’s micro-music-blogging. Now that Twitter has become so popular, there is a whole micro-economy built around Twitter – with multiple companies providing every different style of twitter client that you could possibly want, for just about any platform. Twitter has enabled this economy by providing a rich set of web services around their system that any client can tap into. Blip is hoping to do the same thing. They are providing a rich set of web services around their core that allows any third party to interact with the Blip service.
The current Blip web services are in private beta – and are likely to be extended and modified as the service matures. To use the web services you need to get an API key from blip.fm (via email). Despite the private beta nature of the API – there’s already quite a bit a functionality in the API. Here’s a quick rundown of what you can already do with the API:
- Post a blip
- Delete a blip
- Get a blip by ID
- Get all public blips that occurred over a range of time
- Search for by song or artist name
- User Related Blips
- Get blips for a user ordered by recency
- Get blips for users that a user is following
- Get a user’s playlist blips
- Get blips that have replies
- Get a user by name
- Get a user’s listeners
- Get a user’s preferences
- Get a user’s stats
- Give a user ‘props’
- Save a user’s preferences
- Sign up a new user
- Add a user as a ‘favorite’ dj
- add a blip to a user’s playlist
- remove a user as a a ‘favorite’ dj
- remove a blip from a user’s playlist
- Get a user’s favorite DJs
These services seem to be pretty all inclusive, covering every thing that any 3rd party client would want to do with the blip service.
The Blip services provide output in XML, JSON or serialized PHP. There’s a sample return for a getUserProfile request that returns my most recent blips at the end of this post.
Authentication – In general, any of the Blip web services that are related to a specific user require the call to be authenticated. Creating an authenticated call involves taking a hash of your blip secret key along with a few other fields (such as the timestamp) to create a signature that is appended to the request. (Does anyone else have problems trying to manage these secret keys in an open source project?, they really belong with the code, but if you check them into your open source code repository, they are not secret anymore!).
Terms-of-service – As far as I can tell, the Blip folks haven’t published a terms-of-service for the API. Not surprising since the API is still in private beta. Still, I like to know the rules of the road before I invest too much in an API. In particular, I’d like to know whether or not commercial use of the API is allowed. Blip does have rate limits – no more than one call every 30 seconds per API key for authenticated calls (there are some calls that are excluded from this rate limit).
Documentation – the documentation for the blip service is quite good for a private beta. I especially like the API Tool that lets you play with the API in the browser. They could improve the documentation a bit around what happens with failures – all they say for right now is Error message on failure – which is really not that helpful. In particular, it would be nice if they published a set of status codes that one could expect on error – so I can programmatically tell the difference between an authentication error (a user gave me the wrong password) and a rate limit exceeded error.
Sample Blip return XML <?xml version="1.0" encoding="UTF-8"?> <BlipApiResponse> <status> <code>200</code> <message>OK</message> <requestTime>1234265571</requestTime> <responseTime>1234265571</responseTime> <rateLimit>0</rateLimit> </status> <result> <total>2</total> <offset>0</offset> <limit>25</limit> <count>2</count> <collection> <Blip> <id>16946</id> <url>http://centralvillage.blogs.com/cv/files/vampireweekend_oxford_comma.mp3</url> <ownerId>37237</ownerId> <artist>Vampire Weekend</artist> <title>Oxford Comma</title> <insTime>2008-06-17 12:12:38</insTime> <message>vw</message> <unixTime>1213704758</unixTime> <toId /> <type>songUrl</type> <status>active</status> <reblipId /> <thumbplayLink /> <via /> <viaUrl /> <owner> <id>37237</id> <urlName>plamere</urlName> <profilePic>http://blip.fm/_/images/nousericon.gif</profilePic> <status>active</status> <propsCount>0</propsCount> <countryAbbr>us</countryAbbr> <name /> <website /> <timeZone>US/Pacific</timeZone> <lastBlipTime>0000-00-00 00:00:00</lastBlipTime> <insTime>2008-06-17 09:18:28</insTime> <updateTime>2009-02-05 12:40:39</updateTime> </owner> </Blip> <Blip> <id>16919</id> <url>http://www.notontheguestlist.com/MynameIsjonas.mp3</url> <ownerId>37237</ownerId> <artist>Weezer</artist> <title>My Name Is Jonas</title> <insTime>2008-06-17 09:19:26</insTime> <message>weezer in the morning</message> <unixTime>1213694366</unixTime> <toId /> <type>songUrl</type> <status>active</status> <reblipId /> <thumbplayLink /> <via /> <viaUrl /> <owner> <id>37237</id> <urlName>plamere</urlName> <profilePic>http://blip.fm/_/images/nousericon.gif</profilePic> <status>active</status> <propsCount>0</propsCount> <countryAbbr>us</countryAbbr> <name /> <website /> <timeZone>US/Pacific</timeZone> <lastBlipTime>0000-00-00 00:00:00</lastBlipTime> <insTime>2008-06-17 09:18:28</insTime> <updateTime>2009-02-05 12:40:39</updateTime> </owner> </Blip> </collection> </result> </BlipApiResponse>