i left a post over in the gnucleus forums under the name of Predator containing 3 links to why morpheus should be blocked.

http://216.74.73.125/~c0re/gnuforum/...d.php?tid=2152

Yea, but when they came over with all those users they really kicked vinnies clustering/gain more marketshare plans to dust.
I say leave them alone as long as it still ****** vinnie off.

and let them **** everyone else off as well? thats a bullsh*t solution. morpheus is dangerous to the network. something needs to be done soon.

Something really needs to be done. The results I am getting are crap. Its like what the Gnutella network was a year and a half ago. Damn you Morpheus (shakes fists)!!!!

Everyone is attacking morphues I have asked a question ov kazaa and limewire several times and i still have not got an answer when limewire or kazaa are running in the background my keyboard gets locked out I am running windows xp this dose not happen with morphues I agree that morphues is not what it was but with each new version they are getting better

Why don't you go Download the source code from Morpheus (Freely availible since it's based on Gnucleus) and fix it yourselves and get MusicCity to put it up.

1. the morpheus source on their site is still the Gnucleus 1.6.0.0 code (from what i hear).
2. the code is broken. you cant compile it without errors.

i've been trying to tell people to stop using morpheus since PE came out (cause im a Gnucleus user ;))

Having used several Gnutella clients, gone over to Morpheus/Kazaa, and then come back to Gnutella when Kazaa shut out Morpheus, I've seen enough of both networks that I might be able to provide a few clues.

While Music City talked a good game about all the great new things that were coming to their client, there was absolutely no indication they even had a programmer on staff. All the code came from Kazaa (or whatever its parent company was called). Music City produced nothing on their own. They even stopped participating in their own support forum, the only real support coming from other users and one Kazaa programmer who stopped in once or twice a week.

The point being that when Kazaa pulled the rug out, Morpheus was totally unprepared and most likely had no one readily available to get things going again. That they were able to field an even slightly modified version of Gnucleus in the time they did is a minor miracle. So I really wouldn't expect a whole lot out of Morpheus as far as client updates go. I heard a talk given by the head guy at Music City and it was clear he cared about the users only as a means to put money in his pocket. He is one who will spend not one penny more than absolutely necessary to keep the peasants from storming the castle gates. That's a great attitude if you own stock in his company; not so great if you're using his software.

Also, Morpheus/Kazaa users were not particularly well known for being generous with their files. As I'm sure has occurred in the Gnutella world, there were long, frequently strident discussions in the Morpheus forums about how best to kill the leeches, and whether they should be tortured before being disposed of. The Morpheus/Kazaa network was largely sustained by a small percentage of users who shared massive numbers of files. The remainder of the users were split pretty evenly between those who shared nothing and those who shared a small number of files, probably what they'd downloaded in the last week or so. The observation that connecting to Morpheus ultrapeers results in fewer search results may well be less about problems with the Morpheus client than it is with the Morpheus users. The client can only report on what the users are sharing. If the vast majority of them are sharing just a few files, that could well explain the sparse search returns.

Actually Morpheus is not completely innocent. They even broke Gnucleus (giving every morpheus client the same servent identifier) before releasing it.

The servent identifier has to be unique, for example to send a push request to the correct node. At the moment other servents have to believe that thousands of Morpheus servents using the IP 192.168.0.1 are the same gnutella node.

I was wondering about that. I tried the Morpheus/Gnucleus software right after Kazaa dumped Morpheus and I noticed all those local IPs. Mine originally went out the same way. The thing that surprised me was most everything seemed to work regardless of all the 192.168.0.x IPs. I still haven't figured that out.