John — “Held liable for misinformation and possible losses from it”???

Yes, we’re going to sue you for saying you accomplished something when you may have not actually accomplished it — at least according to my own personal interpretation of “accomplish”. That’s against the law.

Also, we lost a lot of money because you said you accomplished it, and it may not be true, so we’re suing for that too.

What the hell are you talking about???

John, your jealous. Admit it. You sound just like my ex-girlfriend. Trying to grab a little of the attention for yourself? Huh? Feeling neglected? Been working on this for months, and you can’t get it right? Frustrated? I feel ya, B. We’re with you as you try to work through this difficult time.

John! You need to grow up if all you do is hang around blogs criticizing others creativity. Get a life man.

Looks like it’s not that easy to generate “_requests_”. Grow up!

If you’re quite close to completion, why not actually complete the work before going public? Perhaps the request for donations has something to do with it.

As for the media jumping the gun, what was Neowin’s response when you requested that they correct the article?

If you don’t really know “how to generate the license _requests_” it’s too premature to declare that you “are quite close to completion”, isn’t it? Or you guys think that you and only you are saving everybody? And therefore you should be in the center of attention! As far as I know that “_request_” is encoded and unless you find all of the following 3: structure of the challenge, algorithm to encode and public key used during encoding: you can not claim/think/or state that you “are quite close to completion”. Time will tell if you will be able to find at least 1 answer to above 3, not to say that you will be able to find all 3, as you may spend all your life finding just public key which I assume is 20 bytes long.
So, Alex: you maybe right stating that media is “’jumping the gun’ on the story a bit”, but looks like you too by that statement.

As far as I know, nobody on the project has said “we’ve hacked the drm’ all we said is that we are currently in the process of making an app that should provide linux/mac support for napster (and iTunes). We do think we are quite close to completion, but it is the media/blogs who have came out wrongfully saying that the napster drm has been hacked already (and in my opinion ‘jumping the gun’ on the story a bit). There have also been quite a few other astounding innacuraccies, one story even said something along the lines of ‘while a command line version is currently available for windows, the linux version should be available soon’ which is definately not the case, and at the time was completely backwards.

The fact is: he may never succeed. From this message:
http://blogs.law.harvard.edu/cmusings/comments?u=cmusings&p=1074&link=http%3A%2F%2Fblogs.law.harvard.edu%2Fcmusings%2F2005%2F04%2F14%23a1074
It’s obvious that they claimed that Napster’s DRM cracked without really knowing “how to generate the license _requests_”. So basically they haven’t cracked DRM yet, however they proclaimed that they did! What a childish and stupid act. Now, they maybe held liable for misinformation and possible loses from it in addition to possible DMCA and etc. This is plain stupid and for the stupid purpose to be in the center of the spotlight.

“He’ll need both of those.”

If he succeeds, that is. The code that has been released so far doesn’t include any DRM code.

“… and he is willing to “fight the DMCA.” …”

Well, good luck – and many lawyers – to him. He’ll need both of those.

We are currently not certain if the napster-to-go service will work with our current code.

It is my belief (based on napsters compatible players list) that the napster to go service will not function properly with our current code.

But there is at least some evidence to suggest there are non documented backwards compatibility measures in their store. So we will just have to wait and see.

Any code we release to allow the wma files to play on linux will NOT be applicable to existing files not purchased through musik since it is not a ‘crack’ of the drm, it is simply an implementation of the drm decryption.

Our goal is to support all the major music stores in a single framework in python, so that a single app can be used in linux to access them all.