Why block Morpheus, there are other ways to find a smarter solutions for this problems. The problem is in how Gnucleus decides to become an Ultrapeer, I'll add a message I posted in another forum:
Quote:
There is still a problem in the way Morpheus decides to become an Ultrapeer. I think if most clients send the header X-Ultrapeer-needed: false (something like that) to Morpheus, then it will understand it, and would not become an Ultrapeer. Thus reducing the amount of Morpheus UPs.
Morpheus Ultrapeers might also be confused of getting a lot of disconnections and reconnections, because many people are disconecting from them, that might turn them to think that there's actually a need for more ultrapeers.
In this text, when I talk about Morpehus is about the program it self, not it's users.
|
Quote:
|
I was reading the latest Gnucleus source, and the problem seems to be more on the number of leaf that it can have. Because it's deafult is to 400, then it will think it is more powerful than most of the other Ultrapeers. So a better way to get Morpheus ultrapeers to downgrade is if most clients can send Morpheus a header that the other client can host more than 300 leafs, so that morpheus thinks it is less powerful.
|
So a better solution would be to help reduce the amount of Morpheus Ultrapeer than blocking them.
dague12