You Want The Shady S*** Of Es5?

[Hacktown]

Originally posted by NotoriousBIC+19 February 2004 - 11:26--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (NotoriousBIC @ 19 February 2004 - 11:26)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin-Hacktown@18 February 2004 - 17:37
But what he said does make sense.&nbsp; In short, he claims that since no p2p program automatically forces you (when you install the p2p client) to share certain directorys or even share at all, that es5 is no different.&nbsp; He claims they dont tell you what to share or with which network to share.

What SharePro does is equal sharefolder with network resources. Which is a one-sided comparison, to say the least.

For example: An ES5 client d/l a file from 5 Kazaa clients at 100 kbps. Those 5 clients all have a slot less and combined 100 kbps less bandwidth to use for the Fasttrack network. Those resources won&#39;t be shared back, because that&#39;s impossible.

If people want to share they will share. It really comes down to that. Maybe ES5 wants to drain all of the other networks resources til the point that everybody simply is forced to use ES5.

I thought we had enough Microsofts in this world [/b][/quote]
Isnt there a way to place a proper ration system in a p2p network (not in the client) so that people get their even share? I mean the way you describe it that ES5 could very well suck the life out of all the other networks resources and all the files will eventually be stuck on the ES5 network.

Is this a manipulation technique by ES5 to force people into using their program?

But how does the rest of the p2p community stop this? I mean is it even possible to stop them?

[ilw]

Its kinda strange discussing this simultaneously in 2 threads in the same section, perhaps they should be combined? Or would the resulting thread be more confusing?

Putting a reliable ration system in at the network level for a distributed network (like Es5 or kazaa) is pretty much impossible. Various clients implement their own attempts, Kazaa tried the participation level thing, which was poorly implemented and lasted all of about a day before it was cracked. Emule&#39;s is perhaps the best, where each client stores how much each other client has up/downloaded from it, also there is a built in up/download ratio in the program, if you set it to limit your uploads your downloads are also limited.

If ES5 didn&#39;t want to be seen as leeches they should have given this matter a good deal more thought, each network is a sort of community and every client that connects to it is either helping or hindering that community. The response you get if you leech is predictable.