This week I became the proud owner of a Hackintosh (aka Dell Mini9 running Mac OS X). I needed a new laptop, and have pretty much become a complete Mac convert over the past few years, so my options were limited. Either spend $1000 - $2500 for a MacBook, or spend a 1/10 of that on a homebrewedHackintosh. For both the obvious reason of price, combined with the benefits of a small, light, fast (solid state storage) and long battery life, I went with the Hackintosh.
I was nervous for sure, but I knew a few people that had done it and said good things, so now I am paying it forward. Here's how I got a full-blow pseudoMacBook Air for under $200.
Redeem some of my American Express points for a Dell gift certificate (they best you can generally do with Amex points is 1 penny/point and this fit that bill). 20,000 Amex points = $200 Dell gift certificate (that's the max allowable)
Go to Dell.com and order and customize your Dell Mini 9 - the most compatiblenetbook for running OS X (and all of the device drivers seem to work). You need to upgrade to 16GB SSD (at minimum). I also included the webcam upgrade (higher resolution) and Windows XP. The total came out to around $390 (with 2 day shipping). You could get cheaper if you went Linux instead of XP (since you are going to install OS X over it anyway, but I wasn't sure whether I was going to do this so got XP as the backup plan). Enter your gift certificate number and voila... now you are billed only $190.
Wait for you Dell to arrive (mine took a couple of weeks - which they neglected to tell me until AFTER I paid extra for 2 day shipping). Boo Dell!
Dig up (or buy) a larger USB flash drive to use for the install (at least 8GB but 16GB is probably better). I found a 16GB online for about $30.
If you don't already have the RETAIL version of OS X (Leopard), you need to get it... the OEM version that ships with Macs won't work. I saw a special advertised the other day to MobileMe subscribers for $99. Luckily, I already had a copy so I didn't need to get another.
While you are still waiting for you Dell to arrive, get your USB drive ready for the install. Basically, you create 2 partitions on the drive where you copy a bunch of bootloaders and small utilities needed for the install on the small partition, and a copy of the OS X disk ISO image (.dmg) to the large partition. One of the files requires a Windows machine to execute/copy to the USB drive, but you could use the Dell when it arrives (if you got XP on it) or it will also work with Windows running in Parallels or Fusion on a Mac. The detailed directions (and links to required files) can be found here: http://www.mydellmini.com/forum/how-to-mac-os-x-dellefi-installation-t3925.html. There are multiple methods to install, but the single USB drive method in "Section B (New)" is what I followed.
Unfortunately, I made the mistake of not doing the "custom OS X install" (where I should have deselected all of the language packs, printer drivers, etc.) so that made my install take longer (over an hour) and eat up a lot of valuable storage space. So, now I had to uninstall all of the stuff I don't need to free up space (used a program called Monlingual).
Otherwise, I followed those directions and everything worked great. There was one part that wasn't completely clear in Step 7 (how to boot from the smaller USB drive into the Dell's SSD after install - I ended up having to hit ESC and then type "80" to get that option).
After I was done, everything worked out of the box except one minor issue with noisy sound output (sounded like some sort of interference). I read in one of the forums that if you encounter this just put the Dell into sleep mode and wake it back up. Sure enough, that did the trick. Everything worked right away... webcam, sound, trackpad, etc.
All-in-all, this seems like it is going to be a great travel machine for me. My only complaints with the hardware so far are that a) the vertical height of the screen is constraining... some windows are too tall to be able to get to the bottom of (e.g. system preferences) and it takes some finagling, and b) the keyboard takes some getting used to... the main keys are fine, but I am still having trouble finding some of the punctuation and secondary keys.
Now, my list of "must have apps" for your Hackintosh (after OS X install I only have a few gig of space left for apps).
SimplifyMedia - don't waste your limited space on music, just stream from your home library (I also put Playdar on this machine which can serve the same purpose, but that is still very alpha)
Firefox - I use a number of extensions that I really like (e.g. Delicious, Zemanta, etc) and have never gotten used to Safari
Skitch - I can't live without it, although I may see if Jing can replace it since it handles screencasts & image capture
Dropbox (or something similar) - online storage and syncing is a must for a small machine like this.
Tweetie or Nambu - Adobe Airs apps can be resource hogs, so I opted for a native Mac app instead.
Xslimmer - a small utility that will strip out all the bloat from other applications.)
OnyX - a utility that will help you tweak settings and manage resources
MobileMe Account - this makes things much easier when it comes to syncing everything between your machines. It also comes with iDisk remote storage/sync which could eliminate your need for Dropbox.
Skype - I forgot this at first. I actually prefer iChat/AIM for voice and video chats, but Skype is a must have if you do any international business.
I also put Microsoft Office on it for now, although I don't recommend it. I will probably start to use Google Docs more now for this, and other hosted apps for presentation creation, etc. Everything else you need comes with OS X (iTunes, iChat, Mail, Calendar, Address Book, etc.). That comes close to maxing out the on-board storage, but between the online storage solutions and the new 16GBUSB drive I bought for the install process, I think I should be good to go.
A while ago I messed around with the idea of a Twitter bot that, using hashtags, would rebroadcast anything that someone thought that others should know about (e.g. "check out this band they are great"). The idea wasn't that these recommendations were directed at anyone in particular, but instead played upon the human nature of people wanting to tell other people about something they think is great (see latest buzz on Susan Boyle video from Britain's Got Talent).
I only took that original project so far, but today I revisited it briefly and made some tweaks (influenced by the existing Twitter bot @new_music).
Basically, it looks at Metacritic's movie feed, scrapes the scores off the pages (since they aren't in the feed itself) and filters the results to only display the stuff that has an aggregate metascore of 65 or greater. When it finds one of those, it then hits YouTube to pull the trailer for the video. From there it shortens the URL and then tweets the results out at @uncovery.
I may also start to splice in music, DVDs and other content too... but will let this run a while to see how it feels. As always, comments and thoughts welcome.
Just because I have an endless need to tinker, I planted the seed of another idea today. It isn't much more than this so far....
xBetween: "How many times have you heard the phrase “it’s like a cross between…” when you ask someone to describe something to you? That most simple idea, and how it could be applied to the web to help other discover new stuff (or just have fun), was enough of a spark that I went out and got the domain names today for xbetween.com and crossbetween.com (as well as the Twitter name @xbetween).
I’m not sure what exactly, if anything, this will turn out to be. But, I think there could be some potential to create something interesting out of that simple idea."
I'm starting to formulate some more ideas about what this could turn into, but given the idea is still only a few hours old I'm sure it will continue to evolve. Ideas? Suggestions?
I'm not sure what the terms of the deal between the two where, but according to the Rolling Stone article linked above, it sounds like iLike was covering the streaming royalties on the 25 free streams a month the deal enabled and was hoping to make that back in bounties from subscriptions to Rhapsody they drove?
The project is still in it's early stages, but if you are like me then you head is already spinning on where this could go and what types of experiences it could enable.
The endless debate on the best approach for providing music discovery experiences continues rage. This continued with a SxSW panel put on by Paul Lamere (from The Echo Nest) and Anthony Volodkin (from The Hype Machine). For some background, here is their presentation:
My take? There are many ways to classify these different approaches, and some can be considered subsets of others. But, in short there are more approaches than most can shake a stick at... with some of the more notable examples being (as I see it):
"Musicologist"/Expert Analysis - a hundred people with headphones on categorize songs on a few hundred different attributes (e.g. minor chords, upbeat, heavy piano)
Content-Based/Waveform Analysis - a computer looks at the sonic attributes of a song (e.g. tempo, harmonic range, etc) and then looks for other songs that posses similar attributes
Collaborative Filtering - people who listen to/buy/highly rate song X, also have a high correlation to buying/listening to/highly rating song Y
Editorial (e.g Bloggers, Pitchfork, Radio) - some one broadcasts their opinion... "hey, these guys sound like so and so and they are good. I give them 5 stars".
Semantic (e.g. tag clouds) - by matching tags, genres and sentiment keywords (either manually input by users or extracted from web articles)
Curator (e.g. playlist sharing) - community generated "top song" and "just listened" charts, curated playlists, TV/movie soundtracks. These could be actively curated lists of songs (e.g. playlists) or passively programmed by the curator (e.g. "just listened").
Shuffle - just a random selection of tracks from a fixed set of songs
Biographical - this artist you like was influence by this other artist or was also in this other band
Friend-to-Friend - the most common, one friend tells another... "hey, have you heard X? You'd like them".
For each, you generally have two sources of information which to base your recommendations on:
Implicit - input/feedback is collected passively/automatically (e.g. listening history)
Explicit - input/feedback is solicited and manually provided (e.g. user ratings)
Some of the approaches above are exclusive to one type of data input (e.g. "editorial" is explicit feedback only), but most incorporate both.
And, as we speak there are hundreds/thousands of Music Information Retrieval PhD candidates figuring out new approaches, there are new spins (and terminology) on the existing methodologies, and companies combining two or more of the approaches above. Having spent some time in the discovery/recommender space myself, my take is this...
There is no magic bullet.
We all discover content everywhere, and from every context.... friends, TV soundtracks, recommendation engines, radio, etc. In my opinion there is no such thing as a "better recommendation".... there is only a "good enough" (in that what I discovered was satisfying) or a "bad" recommendation. What is required in both cases is transparency as to why it was recommended. I say often when it comes to recommendations... "the why is usually more interesting than the what". That is because the "why" helps user identify the sources that they trust, can relate to, and can be turned to again in the future for inspiration. Sometimes that source may be a machine, sometimes it may be an editor, sometimes it may be a chart. They all have their value, and they all serve the same purpose.. to be one my personal "program directors".
I had a conversation this morning with J T. Ramsay where he told me: "[music] discovery is one of the biggest fallacies of all time. If people were so amped on discovery, radio would have been formatted differently." And I have to admit, I don't disagree.
What consumers have continually asked for is "programming", whether is be playlist builders, charts, "just played" data, recommendation engines, DJs, mixtapes or CDs. Basically, it just comes down to "don't force me to make a decision every 4 minutes about what I'm going to hear next". As music services continue to move to small UI devices where search and destroy is not a viable use case (mobile, car stereos, etc.), programming becomes even more essential.
The title of this post "Program Director > Recommenders" is not meant to imply that they are different and that one is better.... what I mean is that one is a superset of the other. Trying to pit them in a battle with each other is akin to asking... "which is better when you are hungry, a sandwich, a hot dog, or an apple?". The answer for me is, "they will all do the trick... it's just a matter of what temporal mood I'm in weighed against how much effort I have to expend to get each ."
One of my most recent posts discussed (and/or ranted about) "content resolution". In that post I mentioned a very compelling new open-source project called Playdar. This project was started by some of the folks from Last.fm, but is rightfully gaining attention of the digital music innovators very quickly. What is it exactly, and why is it so important?
Playdar is designed to solve one problem: given the name of a track, find me a way to listen to it right now.
It will search your local disk (iTunes library, MP3 folder etc.), it will search your home or office network (kinda like searchableiTunes shared libraries) and it will search other sources. You can write plugins for Playdar to enable it to search additional sources. It's fast. If a matching song is within reach, it can start playing in less than a second.
This is called Content Resolution. Playdar is a "Content Resolver" - it will take metadata (artist, album, track names) and resolve them to a location of a matching music file. This might be on your disk, or over the network - regardless, sources are always presented as URLs that point to your local machine. Playdar runs a lightweight webserver on your machine - this is how you talk to it, and it's how other desktop apps and web apps talk to it.
Playdar has an HTTP API that returns JSON. It supports JSONP, so any website that you authorize can use Javascript to talk to the Playdar server on your machine. This means:
Websites can automatically put play buttons next to songs they reference.
Streaming services and music blogs can save bandwidth by playing you your own copy of a song instead of streaming it from a central server.
A lot of interesting web-app mashups are possible. Pull interesting music data from an API, and play people content they already have.
You could build an iTunes-Genius-like web app using Playdar and the Last.fmAPI, all in-browser.
You could build a playlist sharing site that shares playlists, not mp3s. Think muxtape, but it will only play songs found on your machines.
If you run Playdar on your laptop and desktop on the same network it will take advantage of songs on either machine.
Music on the web can be marked up so you can always take advantage of local content."
Sure, there are other remote access/webserver solutions out there that enable you to access your content (and your friends') remotely - see Simplify Media and Orb. And there are P2P clients and torrents that enable you download virtually any song available. But, what gets me excited about this is the single interface with cascading resolution logic that it enables - and how it can seamlessly integrate the (existing) web with local/network/free-range/streaming service content. In short, it keeps checking sources in priority order until it finds what it's looking for.
It fosters the development of sites and apps that can add value with context (editorial, informational, social) and discovery features without putting them in a position of having to deal with content licensing and streaming costs.
It has the potential to drastically cut costs of existing music services since they wouldn't have to foot the bill (both royalty and bandwidth) to stream content to users that they already have - thereby helping enable more viable economics around music discovery and sharing sites. Or perhaps lets existing music content sites exit the content licensing/streaming business altogether (some speculate that Last.fm's recent moves away from free streaming everywhere but US, UK and Germany are the first step in this direction) and instead focus on adding value *around* the content.
Sites and applications without their own music content could be marked up to support Playdar... adding click-to-play scenarios in Google search results, Facebook, Twitter (site and apps), IM clients, Wikipedia, news articles and more.
It promotes the use of standard markup to identify music content (e.g. hAudio, XSPF, etc.) that enables users to share content (links) and playlists across different service providers. You keep your provider of choice, I keep mine.
It could be extended to support comparison shopping of content across multiple vendors.... e.g. "just give me the cheapest MP3 provided that it is at least 256kbps".
It could tie into your existing social graph, giving you a single view and interface into all of your friends' local/network content. For example, you see in your AIM status that one of your friends is listening to a certain song... you click play. If you have the song, it plays from your machine. If you don't have the song, it streams to you from your friend's machine, if that friend doesn't have a local version of that song then it streams from another friend's machine that does have it. If none of your friends has a local copy of the song, then it finds it on the web. You don't need to know where the song is, Playdar does the work of finding the best source for you.
It could enable the darknet, where you can get access to all of the content on not only your and your friends' machines...but also the friends of friends (of friends). All unmonitorable and untrackable (unlike torrent sites) since each person only accesses content via people they trust - no one in the chain has knowledge of where the content originated from or where it terminated (see OneSwarm for more on this). Taken with the notion of "six degrees of separation"... you theoretically could get access to any file/song from anyone in the worlds in 6 hops or less.
There are a lot of directions this project could be taken and extended, which is the beauty of it being open-source. Have some ideas? Contribute.
In my opinion, this has the potential to be one of the most disruptive music/tech developments we've seen in a long time.
I've decided to expose a bunch of the pieces behind my "Playtapus Project" on a new wiki at: http://playtapus.pbwiki.com/.
My hope is to get some more people involved - hopefully some that are far more proficient at writing code than me - as well as anyone else that has ideas or/or the talent to help those ideas to be realized. I'd love to see where a group of people can take this, and whether it opens all of our eyes to any new opportunities.
I am a closet brand marketer. I often create "brands" (OK, I make up words - usually by combining multiples that when pronounced sound like another existing word) that I think could be interesting or evocative. Over the past decade, I have kept a running list of potential brand names (or tag lines) for the most random things... from fictional band names to non-existent apparel companies to portajohns (toilets) to my own music/tech aggregator "mediaor" (pronounced like "meteor").
As backwards as it sounds, sometimes these words provide a spark for a product idea that I may explore in the future (yes, I have a separate list for those).
For the "brands" that I think have some real potental (or just amuse me) I will go grab the domain name for too. In my opinion, the most promising ones are the ones that express an idea or feeling ("Google", "Amazon", "iPod", "Twitter"), not a literal product implementation or feature ("Search.com","Toys r Us", "CDnow") .
What does this have to do with anything? Well, I have been struggling with how to refer to my latest projects (e.g. "friendP3", "meP3", "ambient signal".). The labels of the implementations were constraining the larger ideas around passive publishing, content resolution, data aggregation and portability, the social graph and sharing. I know some will say that is stupid... "why try to brand it at all?". Well, if you want people to talk about something then I believe you need to provide them a common lexicon to do so (it also helps people find and track the conversations on topic - see Twitter).
So, now that I have made a short story long, I come to my point. For now on I am going to be referring to the collective of my recent music/tech science experiments as "Playtapus".
Yes, it is a combination of "play", "tap" and "us"... but also more a play on the fugly yet lovable platypus. No one is quite sure what it's place in evolutionary history is, but if nothing else... it's at least interesting. Really all this project aspires to be...
For those of you that know me, you've probably heard me ramble on for years about how we need to decouple media content and the service from whence it comes. At the drop of a hat I will often start spewing off the same tired example...
Imagine your music service of choice is Rhapsody and mine is iTunes. Or your use iLike and I use Last.fm. You use Spotify and I use Imeem. Or you use Blockbuster and I use Netflix. I should be able to follow your tastes, history and recommendations without having to join your service (or vice versa). We are now starting to see some lifestreaming apps/aggregators that solve the first piece of that puzzle.... I can see what you what media you are consuming without having to join your service.
But, currently when I see that you've played a song that I want to check out, the link takes me to your service provider, not mine. Sure, this is in your service provider's best interest (page view, conversion opportunity, etc.) but certainly not in mine. Now, I have to copy the info, got back to my service provider, and manually re-enter to find and acquire.
The way it should be (IMHO), is that the consumer of the media should get to decide what service provider fulfills it. Basically, it's a massive translation layer that can take content in from anywhere and map it back out to anywhere else.
In the absence of these "portable music identifiers", people that are passionate about greasing the wheels of taste and content sharing are forced to the lowest common denominator... MP3 search engines. This has been the basis of the projects I've been done recently.... mapping multiple services play history down to free-range MP3s (or at least what it could find). Of course, the rights-holders are not big fans of this approach (see "world vs. seeqpod" suits) - and the consumers are often frustrated by bad files, dead links and just poor overall quality of content delivery.
I've recently been vocal about the idea that the solution to this problem is an API platform that any/all services could use in lieu of MP3 search. Conceptually, an advertising/commerce supported (ok, subsidized in the near term) free-streaming catalog provider that most music could be mapped to - a fully licensed central digital music catalog(more on this later). Granted, this is a rather grandiose idea and anything in this industry that upsets the status quo is often met with resistance (at best) and endless lawsuits (at worst).
So, my rambling has finally led me to my point... content resolution. If there is no central catalog that everything can be mapped to, then what we need is that translation layer that lets content links be mapped back and forth across endless catalogs. Grandiose? A bit, but seems accomplishable without buy-in from the existing establishment. In fact, there is the very early stages of an open source project called Playdar whose goal is to provide the framework that lets content be mapped from one source to another - from the web to your local library, to your other networked devices, to your friends' machines, to music service providers, to search engines.
I'm pretty excited by the idea - I think it could enable some very compelling consumer experiences that the community is empowered to enable on their own.
Yesterday I talked about how I wanted to be able to use the track and artist name from the currently playing track in iTunes to automagically find/publish a free-range MP3 link for that track to Twitter. After digging around into AppleScript this morning, I'm happy to say that I've got it basically working (see screencast).
I'm guessing there is probably a more elegant way to do this, but the Frankenstein continues to grow appendages. Take a look and let me know what you think.
It adds active publishing to the passive publishing that I'm doing from aggregated play data from multiple music services. So, when you are thinking of a song you just type it in, and it looks for a free-range MP3 version of that song, shortens the URL, and formats it so that playTwitter knows how to deal with it. This is similar to what I talked about before except I have automated the formating, finding and posting to Twitter to make it more user friendly.
I've also added a field that let's users create collaborative playlists using Twitterhashtags (see previous post). This lets any/all people to add songs to a particular playlist. For example, see the "bestof2009" playlist. By default anyone can add songs to this playlist just by using the same name/hashtag. Well, that's great, but what if you don't want other people's junk in your list? Just use the "advanced search" features of Twitter Search to filter it down. For example, here is the list with just my contributions.
Just like on any other webpage with MP3 links, the playTwitter bookmarklet lets you "play the page". So, filter it however you want, then play it.
Collaborative playlists are a great idea that often gets bogged down and limited by the fact that everyone has their own music service/platform of choice and there is generally no interoperability between them. Fred Wilson blogged on the topic, and the challenges, about a week ago. The problem is that most collaborative playlisting options require a lot of overhead... either everyone needs to join/use/switch to the same playlisting site or the creator of the playlist has to engage in a lot of manual labor to curate the playlist.
I talked a bit recently about how some service are already set up to handle the exact use cases that people are interested in, just that the other pieces of the puzzle haven't been put in place yet. By using the "web as the music catalog", listening data as automated search queries and free-range MP3s as the universally supported format, it is actually easy to create collaborative playlists with a combination of existing technologies that can all work on a common platform. Hashtags, Twitter Search (aka Summize), friendP3 and playTwitter.
To create a collaborative playlist, one just needs to manually post (or retweet a friendP3/meP3 link) with a playlist name as a hashtag. For example, I just started one with the name of #fp3Bestof2009 (where "fp3" stands for "friendP3"). I posted a couple of songs, and others can as well without any overhead required by me to manage. To see the collaborative playlist, I can use Twitter Search to search for that hashtag/playlist name. http://search.twitter.com/search?q=fp3Bestof2009
Click on the playTwitter bookmarklet and you are off and listening to the community programmed list that continues to be dynamic over time. If you want to filter the playlist, you can simply use the "advanced search" fields of Twitter Search and you can limit posts/songs by contributor, date, keywords, and more. Find a filter you like, and then you could subscribe to the RSS feed for those filters and just watch what continues to come in from users across the web.
User friendly? Uh... nope, not yet. Powerful? I think so. What do you guys think?
I've been publishing my meP3 stream out to a bunch of different platforms (e.g. FriendFeed, Tumblr, Soup.io) but the one that I'm most fond of right now is the Twitter station that I'm passively programming @ambientsignal. There are actually many parts of the experience that are substantially worse on Twitter than on the other platform - most notably the lack of an integrated media player - but you've got to go where the people are, right?! A quick addition (and hopefully future evolution) of playTwitter and StreamPad (shoutouts to both Lucas Gonze and Dan Kantor) could make this even more powerful.
While I was originally focused on constructing a station by crawling a single user's social graph, I've shifted focus a bit more to the simple aggregation of a users *own* stream. Each user can publish their own, then just simply follow the others they want. Where I think it could get really interesting is in Twitter clients. Each user could create their own "group stations" comprised of any single or collection of meP3 streams. Then just throw a small media player into those Air and iPhone apps and you've got a social listening and discovery service that I think would be as compelling as any out there. TweetDeck, Twirl, Twitterific, et al... are you out there? Not only does it power great content discovery (I've personally been exposed to at least 5 new bands that I like in as many days from @friendP3), but it would/will stimulate endless water cooler conversations around the content.
My friend Dave now is also powering his own Twitter station @ZprocketRadio. It's just starting to load up with tracks, but when I hear something I like I will inevitably reply to @ZprocketRadio with a 140 character note on what I think about it. He also has brought up some interesting ideas around the use of #hastags to power collaborative playlists that I may play around with today.
If anyone out there is interested in being one of the first stations (or wants to build a killer Twitter Radio client) drop me a line at jherskowitz (at) globallistic (dot) com and I'll help you out. It's still super-hacky and exceedingly geeky... but I'd be interested to see if a community evolves around this concept.
When you are just a guy trying to hack something together in your free time, you are quickly and constantly reminded to not reinvent the wheel. That, along with my complete lack of programming skills, forces me to brute force and re-purpose stuff wherever possible (see last 5 posts or so for proof).
The great thing about that, is it helps open my eyes to features/products out there they will perfectly handle the use case I'm looking to implement. The newest ephiphany is that Twitter's "favorite" feature is ideal for creating a playlist of favorite songs that you may hear on @friendP3 or any other "twitter radio" station (current or future).
(by the way, I *love* Jing's screencasting app but they fact that the videos aren't resizable is a major problem since they are all too big - dimensionally - to fit into my blog)
When you deal with hosted MP3s you are reminded how much you *could* do with music if all of the shackles and protections were removed (e.g. DRM and required Flash players). Here is a video highlighting how things "just work" on your mobile...
There is no reason that this same scenario won't/doesn't work with simple SMS alerts, email, IMs, etc. The only real work needed is for playlisting of these tracks to be supported in these apps...
The latest ingredient in this grand mashup experiment I embarked on last week is what I'm calling (for lack of a better term right now) "Twitter Radio". The idea being that a user can either passively, or manually, program a soundtrack as a backchannel to their tweets. This can either be done for you personally - with links to songs you listen to systematically injected into your regular twitter account or into a secondary dedicated "radio" account. Also, collaborative "group stations" can be automagically programmed by the listening behaviors of one or more people and posted to a Twitter account.
For now, I'll probably use a secondary dedicated account (TBD) so I won't overwhelm everyone that follows me @jherskowitz. Once it's more stable maybe I'll integrate them... too bad Twitter doesn't have filters that could better handle this scenario.
To listen to one of these stations first-hand, you just need to do a few things:
Clock the playTwitter bookmarklet in your browser's link bar (after dragged there in step 1)
That's it... now you can listen to everything that shows up there. There is still plenty more I would like to have it do... but it's a start. And as with all things that I hack together, it will probably break more than once... but I'll try to fix the stuff as I can.
So, if for example your username on Last.fm, Hype Machine and Pandora were "fredwilson" and you didn't have any accounts at, iLike, Imeem or Rhapsody, then your feed would simply be:
Note that most parameters are your username, but both Rhapsody and Imeem IDs are harder to come by. Your Rhapsody ID is found in your My Rhapsody RSS feed URLs. Your Imeem account number is even harder to find, but I'm working on trying to find a better way to get to it.
If you can then take that feed and do anything you want with it.... embed in a widget on your blog, feed it to Streampad or Yahoo Music Player, subscribe to it as a podcast, dump it into your lifestream, feed it into your Twitter account, etc.
One thing I was thinking about is playing around with "rooms" on FriendFeed to see how this would look as a collaborative "station". Other ideas? I'd love to hear them.
UPDATE: I found some issues with the way I was dealing with and rationalizing dates across all of the services. This needs more work and until it is fixed you may see stuff jumping around in time like the castaways on "Lost".
My experiments involving the social graph, aggregation, data portability and MP3 search continue. I've now got my Imeem just played feed automatically producing MP3 search results as well. Unfortunately, I don't yet see a way to easily get your Imeem UserID from your username/login info... so it's not really user friendly for anyone else at all at this point since I had to manually dig mine out and hard code it. Regardless, I've added it to my lifestream and it seems to be working as well as the others.
Unfortunately, Soup.io (my current publishing platform) nor Tumblr seem to be able/want to keep up with the feeds. That being said, I'm also pushing my aggregated MP3 stream to some other lifestreaming services that seem better equipped to keep up. FriendFeed feed seems to deal with it pretty well (http://www.friendfeed.com/jherskowitz). And while Lifestream.fm (http://lifestream.fm/jherskowitz) won't embed a flash player in the stream automatically like FriendFeed and others, it does have a cool feature (powered by Beam-It-Up-Scotty) that lets you send links via SMS to anything in your or others' lifestream(s). So if you see a song you like, you just "beam it" to your phone, click on the link, and listen to the track stream over the air. Pretty cool.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=dad500d0-b5c2-42ec-8e09-8bcdf2607755)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e1e04c80-be6d-4153-8c6b-83bd700636fa)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=9637d0d6-a84d-40d8-b91a-b68f80ecc105)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=2e061d1d-a0a8-455c-bc05-41cd617b85c5)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=58389dff-0bb6-4fcf-9c0e-be936ef9e32b)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=0f49b03a-ae12-4aa7-b457-b0587a070840)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c2bec6f6-eaf6-4d1e-bd2c-06a1af93c60b)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=6b3fb05c-352a-44e7-885a-5c075bd454bb)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=5e820d64-4e3a-41dc-9a04-cac2da9b2091)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=cd737d28-db28-4ed7-852a-e53344252ef9)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=21d4f4ce-366f-49be-9a81-a39e20888767)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c781c29e-9748-4d50-907c-5e603b4ac5ed)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=cb9734f4-a2a6-4aa7-915f-8c262f491023)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=1862cf4c-43c3-4b35-b988-50f63237cbe3)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=b9b40481-a8fb-4d6c-b458-2899a26a117b)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=ee8c565b-b303-4af3-b6b0-df0775c54276)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c801a107-ba20-4fa5-9794-e8c8be33ed8d)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=29be7491-36d4-4af5-940a-bb4395bbfcad)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=37b17beb-294a-429c-a895-a0e9195b38e3)