Slashback: Picnic, Neonapster, Microsoft

Slashback tonight with some good news about Linux Weekly News, an annual update for interested picnic-goers, a followup on Neonapster, and a few words of caution on Microsoft's approach to code disclosure. Read on below for the details.

Look at the nice horse they left. babbage writes "As part of ongoing antitrust settlement arrangements, Microsoft has 'opened' the source code to some of their protocol implementation source code. Go ahead and read the license -- but do keep an eye on the NDA you have to agree to first. If you find an NDA to be an objectionable first step -- and I'll admit, I haven't read the license because I don't agree to the NDA terms -- then speak up about it. The Department of Justice is accepting public comments from industry professionals about the new licensing terms. There is a real concern that such pseudo-open licensing could effectively scuttle development efforts on projects like Samba & Mono, but we need to get open access to the license in order to figure out what the risks are. If you have anything to contribute, now is the time to speak up to the DOJ."

Bring your own herring. Bill Kendrick writes: "From the folks who brought you the immensely popular "Linux10" event, comes Picn*x11, a picnic/barbecue celebrating 11 years of the Linux operating system. It's going to be held in Sunnyvale again, the Saturday after LinuxWorld Expo. So go RSVP now, and get your Picn*x11 t-shirt! (Proceeds go to EFF)"

With enough eyeballs many programs seem shallow, too. TheMMaster writes "Neonapster seems to have GPL'd their software, you can download the source here, not that I am terribly happy with what happened, but at least this seems to have been settled out of court ;) of course... it is still a cheap cdex rip off ;)"

LWN is good reading. Keck writes "We all shed a tear for Linux Weekly News a little too soon maybe?

Yes, we know we said there would be no LWN.net Weekly Edition this time around, but, in the end, it was worth the trouble to put together a mini version. So here it is; with luck, the full Weekly will be back on August 15. "

Comments

Problem number one...

[killthiskid]

Well, I started to read the license, but then I got caught at part one of step one:

Authenticate with a Microsoft Passport.

Well, I guess I'm out...

Re:Problem number one...

[WEFUNK]

If you decide to continue anyways the next page begins:

Microsoft Communications Protocol Program
NDA Request Form Instructions

The first step in the Microsoft Communications Protocol Program is to obtain and sign a Non-Disclosure Agreement (NDA). To request an NDA, click on the link below and complete the request form... to facilitate confirmation of your request and avoid possible delays, it is important to use a Passport account with a verified e-mail address from a domain used by your company. Requests submitted using e-mail addresses from unrestricted or anonymous email domains (e.g., Hotmail) will not be handled without direct contact and verification from the company involved.

...and I thought my Hotmail account was my Passport. Well lets try anyway...

If you keep on going, logging in with your Passport you'll probably hit this page:

Microsoft Communications Protocol Program
NDA Request -- Passport Configuration

Which basically asks you to set up your Passport account to share your personal (although probably inaccurate) information with all Passport Services before you can even get to the protocol NDA request page...

Ummm, No thanks.

Difference

[Anonymous Coward]

Neonapster is not a rippoff of cdex...its a gnutellla filesharing app....its NeoAudio thats the Cdex ripoff...i recommend cdex to anyone ripping cds, ive used it for year and its great

The source code isn't new

[spectral]

The source code [for NeoNapster's softwares] has been at that exact same link since the story first hit slashdot front page. It's just some people are too quick to yell about violations, and not check what's actually going on. So yeah, it's good a "front page" story cleared up the issue, but it shouldn't make it sound like they just changed it, since it's been there the entire time.

Comments at download.com

[Mr. PJR]

Those of you who registered your disgust with NeoAudio at download.com might want to take a look at the comments page--every commment prior to 7 August has been deleted. Magically their rating seems to have jumped. go figure http://download.com.com/3302-2140-10137006.html

CDex author warns of using NeoAudio

[Istealmymusic]

cdex.n3.net has been updated with a message from Alber L Faber:

There is an application called NeoAudio, which is a straight CDex rip off. They changed some string (i.e. replace CDex with NeoAudio), changed the logo and added some nice SpyWare and Adware. I contacted Richard M. Stallman about this issue, but unfortunately I can not do much about it, except for the fact that they are removing/changing copyright strings which they should not. So please do not download and install NeoAudio (they probably make quite a few dollars by shipping the adware) and also advice other people NOT to download NeoAudio either, and warn innocent users not to download this application but download CDex instead.

In addition there is a small but worthwhile discussion over at Freedb. Some Slashdotters have missed the fact that Mr. Faber does not claim NeoAudio violates the license, he is merely suggesting potential users make informed decisions on whether to use CDex or NeoAudio. Logically, there is no reason to use NeoAudio -- it offers no improvements over CDex.

Of course, there's always Exact Audio Copy, which has proved itself in the mp3 scene as the de-facto standard for ripping.

Microsoft: worse than before

[Andy Tai]

The "opening" of the protocols actually extends the power of Microsoft over third parties. Previously one can implement the protocols in a clean room manner and does not need to deal with Microsoft. Samba, for example, implemented CIFS on their own without depending on any help from Microsoft. Now if you sign on to this Microsoft program you essentially recognize Microsoft's claim of ownership over many protocols. You have to sign an NDA first, and then who knows what will be in the actual license agreement. The anti-GPL CIFS protocol license is a clear example of the kind of restrict licenses Microsoft can put out.

Standard protocols should not be owned. Now Microsoft is trying to use the settlement with the DOJ to actually extend its IP ownership to common protocols, beyond actual source code/implementations. Microsoft's power over third parties and the market actually increases, contrary to the original motivation beyond the anti-trust suit.