Whamb Audio Player Shares Via Rendezvous
Stéphane Thiell writes,
"I just released an update of Whamb, a little shareware CD/MP3/OGG player for Mac OS X 10.2. It's not as advanced as iTunes, though it now has playlists sharing using Rendezvous.
A friend even wrote a tool in Perl which allows to run playlists
server on POSIX systems." Nifty. It's still in development, but works pretty well. I've got the Perl daemon running too, with some local modifications. The Rendezvous support has some scalability issues with my 25GB of MP3s, which maybe why iTunes still doesn't have it ...
Well, I just d/led this and I can't say I'll too impressed. It's cpu-usage is just a little under iTunes (avg. 6% to iTunes avg. 9% on my MDD 867). The rendezvous thing I'm sure is cool, but I have no way of testing it out. It plays the same files iTunes does. And skinning is pointless because I prefer to use synergy for iTunes.
No offence to the author of this app, but I don't see why anyone is trying to charge people money for such an application ($12.50 USD in this case) for a replacement of an excellent tool Apple gives away for free.
sin(6cos(r)+5A)
Still, it's got OGG, so good on ya.
If Jesus wants me it knows where to find me.
Unfortunately, the installation procedure isn't drag & drop. I pretty much expect that in any application I'd be willing to pay for. It could be done easily with Whamb as far as I can see. If they really want to store the skins in the ~/Library they should do that on first run. Personally, I think they should store them in the application package.
I have a website. It's about Macs.
This gave me an idea.
The primary problem in systems like Freenet is a reliable way of obtaining an index of all the information available. e.g. *this* SHAsum is *this* mp3.
What if players could share playlists, which contained SHAsums of each file (or series of chunks in the file, whatever). This data is lightweight, and free and clear to distribute. Fine to put on an out-in-the-open sharing mechanism. Then the actual audio files are shared via Freenet, looked up using the SHAsums.
Second, there's a great quote from the article:
The protocol used here (WHSP), similar to HTTP for requests, and using XML data for responses, is light and efficient.
I didn't think I'd ever see "XML" and "light and efficient" in the same sentence.
May we never see th