I booted up Xolox this morning to receive the message that Xolox was being discontinued as of 12/1.

DAMNIT. I've only been using Xolox for about a month, but recognized the framework as the saviour of p2p bandwidth and stability problems.

What gives? Who is suing you guys?

why not let it run without support? I guess this means will will never get a version that works correctly

as far as i know, gnutella is a decentral p2p protocoll, that means that there is no server you can shut down.

so i am a bit confused that you want to discontinue xolox and not only stop programming.

and what about stopping the development and release the source code as open source....

xolox is the best gnutella client that i know. it would be very bad for me if it wouldn't work any more...

i hope this is just some kind of sick joke. i agree that it could be ran un updated. this program is very promising.

If WinMX 3.0 ever comes out and it's as good as they say it should be, I won't miss XoloX one bit.

Read the current startmessage from XoloX here:
http://www.xolox.nl/info/default112.htm

Some more links, a dutch court has cracked down Kazaa, Kazaa and Xolox come both from the Netherlands:

http://www.zeropaid.com/news/article.../11292001a.php
http://news.cnet.com/news/0-1005-200...html?tag=mn_hd
http://www.theregister.co.uk/content/6/23107.html
http://www.webwereld.nl/nieuws/9357.phtml (in dutch)

I'm wondering if it really will stop. They "ask" us not to start new downloads after that time. Perhaps this is just legal CYA. "Well Judge, We did what we could and we asked them to stop..."

Personally I don't see how Gnutella is at risk since it is a completely decentralized system. Napster was centralized and it died. Kazaa is mostly decentralized but they switched to central user authentiation recently (mostly to knock out non-licensed clients like the Open Source Linux client). This is where they made their mistake.

I seems to be that the RIAA has only attached centrally managed systems and I don't see how a Gnutella client is at risk. After all, the client is not good or evil, it depends on how it is used.

Well, that's the $64k question. Does the Xolox client contact the Xolox servers at some point, to get hosts or something .. obviously, it is grabbing that notice that appears on the Search page from somewhere on the net. What happens when that http GET fails?

I guess I'm more concerned about how Xolox gets its host file. Most p2p programs go out to some service, like connect1.bearshare.net or some such. Dunno how Xolox gets theirs.

http://www.zeropaid.com/news/article.../11292001a.php *sigh*

Xolox has the ability to download updates when they become available. If they are forced to stop all xolox clients, they might build this into a new final update. The file downloaded is called xoloxupdate.bin It searches for xolox.exe, and uses the downloaded bin file to update it. I suggest you rename xolox.exe to something else and set it to read only just as a precaution....