First of all I want to thank those who did congratulate me by Facebook because of my birthday 🙂
Next, I really love Spotify. I love it so much that I have been using wine lately for it to run, and I am even a Premium user. I have been always annoyed because of using wine for this purpose. Still, I think paying for _the service_ is fair enough, and I didn’t care too much about the client itself, what is important.
Some days ago I started a Spotify client for KDE (called “Spokify“). It is getting in shape, and well, it plays sound using Alsa for now (Phonon or QtMultimedia wasn’t enough when streaming, as far as I have seen, but I will keep an eye on them). It also can search, load your playlists, filter (this isn’t implemented in the official Spotify client!), load and show covers.
I am going to improve it to the point that I can assure it does the same things as Spotify, and more. Next steps are to include KWallet and probably some configuration options.
Some people have asked me why I have started a new application instead having developed an Amarok extension. Well, (and I don’t expect to start a flamewar here, please guys, don’t follow this path), I believe Spotify service is absolutely all I need. I for sure don’t need so many features that Amarok provides, and I wanted to start a small application that has a very well stablished goal.
For those who really care about their freedom, they are free to use libopenspotify 🙂
The bad part of the story is that for you listening to music using Spokify you will need to be a Premium user because of the library restrictions (Application Key, better said).
I still wonder why I have developed Spokify. Spotify service is very restrictive with the libspotify library usage, and they force you to have an appkey that you need to set on compile time.
Only Premium users can have an Application Key. So, my question here is: how is this thing going to be packaged, if ever ? I should assume the packager will be a Premium user, or in that case I could give him mine ? (since in the license, it is explicitly said that team coworkers can share the same Application Key, despite it being private and personal).
I think following this reasoning, the despotify developers have their Application Key directly on the project repository. I am not that brave. I have added an empty file with an #error that asks you to read HOW_TO_DEVELOP file. I can’t assume everyone that clones out my repo will use that Application Key for “legal?” stuff. Since I don’t want to be banned, I keep the Application Key secret.
PS: If you try to compile Spokify, you will probably fail 🙂 I have written a patch for kdelibs that is not still in kdelibs trunk, but you can have the patch here.