P2P-Zone - View Single Post - A plan to revive old Morpheus 1.3.3 and avoid KaZaA's "Upgrade Morpheus" trick

Spikologia · 14-04-02, 01:05 PM

Snowman - I understand what you're saying, and this is why v1.3.3-based "iMorpheus" keeps dying.
But this is where my "discovery" comes into place. v1.4 isn't blocked by v1.5+. And probably v1.4 doesn't block v1.3.3, as v1.3.3 wasn't blocked by it before. What does it mean? First we distribute lots of v1.4 clients. Those will have no problem connecting to the COMPLETE KaZaA-Grokster-iMesh FastTrack network, as v1.4 CAN be connected to v1.5+ superepeers and isn't locked by them.
Later, when enough v1.4 clients are online, Morpheus could be used again, first connecting to v1.4 clients and later to other v1.3.3 clients, Morpheus could use v1.4 superpeers as gateways into the whole FastTrack network, and therefore will not suffer the fast death of a small "independent" network.

14-04-02, 01:05 PM	#7
Spikologia Registered User Join Date: Apr 2002 Posts: 19	Sure will work, snowman Snowman - I understand what you're saying, and this is why v1.3.3-based "iMorpheus" keeps dying. But this is where my "discovery" comes into place. v1.4 isn't blocked by v1.5+. And probably v1.4 doesn't block v1.3.3, as v1.3.3 wasn't blocked by it before. What does it mean? First we distribute lots of v1.4 clients. Those will have no problem connecting to the COMPLETE KaZaA-Grokster-iMesh FastTrack network, as v1.4 CAN be connected to v1.5+ superepeers and isn't locked by them. Later, when enough v1.4 clients are online, Morpheus could be used again, first connecting to v1.4 clients and later to other v1.3.3 clients, Morpheus could use v1.4 superpeers as gateways into the whole FastTrack network, and therefore will not suffer the fast death of a small "independent" network.