How to make Imorpheus work again. My theory
I have been following the events with IMorpheus .
Too bad it doesn’t work anymore, because maintaining such an indepent FastTracknetwork would be a breakthrough in filesharing. Don’t know if you know the confidential RIAAmemo about the FastTracknetwork. It contains some usefull information about the structure and procedures You can find this article at http://www.dotcomscoop.com/riaamemo.html What I get from this it that Morpheus connects to a central login server owned by MusiscCity. If this server is down, Morpheus connects to the supernodes that are mentioned in the registry. My theory on what happened is that StreamCast/MusicCity closed down their login server last week. That made users of version 1.3.3. connect to the supernodes., thus creating an independent network. StreamCast/MusicCity has found out what was happening and has rebooted the login server. Morpheus 1.3.3.connects to this server and this login server somehow prevents that you connect to the supernodes. How to solve this. The Ipadress of the login server is hard coded in the application. If we can find a way to remove or disable this piece of code, Morpheus might try to connect to the supernodes again. Unfortunately I don’t know how to do this , maybe one of you guys has the necessary knowledge or know someone who can do the job. I'll be happy to test it. |
My theory is that a Kazaa SuperNode or Nodes has again "poisoned" the network. I don't think this is anything to do with Streamcast or MusicCity at all. They've washed their hands of FastTrack. There's no reason for them to get involved.
If you read the article further, you'll see that if none of the preset supernodes in the registry is functional, then the client still links to a Kazaa IP address to get a list of supernodes from there. I'm not sure of the solution to this one. But clearly the network isn't as "self-organising" as we were lead to believe. I see the possibility for a shadow network existing though, we just need some way of securing the supernodes, and disabling the hidden link to Kazaa forever. However I do feel that intrinsic within the Morpheus client is the potential for external tampering, so if iMorpheus is ever to have a future someone needs to reverse engineer the client and publish the source. Time for the big guns! |
First of all, welcome aboard guys and enjoyable stay at Napsterites Underground to you both! :beer:
Quote:
- tg ;) |
Quote:
The network_config that was modified a couple of weeks ago and is currently the one I see in my registry for both Grokster & iMesh started out with a message from KaZaA about updating to the "KaZaA Media Desktop" (KMD) - but both Grokster & Morpheus directed you to their own website for an update (possibly a message written in the program itself?) Two days ago when the old Morpheus quit connecting again I looked at the network_config again and this time it had a Grokster ver. 1.5.1 update message! I wrote my backup network_config back into the registry and after about 20min got the "Client too Old..." message, but now it has the KMD Update message - However it still tells you to go to MusicCity for an update... :PO: Update - All 3 are now showing the "KaZaZ Update Message" & the "Grokster Update Message" - The Grokster message was not in there when I extracted the information below... I have the KaZaA message, but it will take a little bit to do the Grokster... |
Quote:
Quote:
Quote:
You can also see the SuperNode that switched |
>>>warning does not address the main topic<<<
Quote:
Quote:
Edit: in looking for more info at the dotcomscoop site, the author made similar conclusions in this march 5th 2002 article: http://news.dmusic.com/article/4556 also: Quote:
|
All times are GMT -6. The time now is 09:03 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
© www.p2p-zone.com - Napsterites - 2000 - 2024 (Contact grm1@iinet.net.au for all admin enquiries)