BitTyrant: The 'Selfish' BitTorrent Client > sounds like Emule/Edonkey

sounds like Emule/Edonkey

Hmm.... I really don't have a problem with eMule myself. Yeah, you gotta let it run for a bit before the downloads start, but everything comes through. It works MUCH better than torrents for any files that are less than popular, because it is specifically NOT designed around swarming. Swarming ensures popular files are fast, to the exclusion of unpopular stuff.

Of course, if you have problems never getting downloads in eMule, perhaps you should remove draconian limits on how much you're uploading. It really DOES make a difference.

Does this belong in torrents? Only if you want to change the nature of the network. As I understand it, "Super Seeding" does a similar job as this, ensuring that only clients who are uploading chunks back to the network get chunks. However, this only works with the initial seeder. The idea is that once everybody has a copy of the file, the swarm has "started", and at that point, it is fair for all. Myself, I've never had a problem getting any halfway recent files to download on torrents either. I'm not even sure I could get files any faster with a "selfish" client. You see, I already am able to saturate my 6mbit if I want, and I just don't have anymore capacity for downloads. So why cheat?

reply to SmD Frylock
emule/edonkey networks are insanely slow becuase of their QUEUE system. bittorent does not have that. if you were paying attention to (offical) edonkey client development, you'd know that shortly before their shutdown they were experimenting with modification similar to bittorent's 'optimistic unchocke'.
--
[Sig removed by Administrator: Signature can not exceed 20GB]

it never used to be that way pre QR.

When edonkey first came out, the only thing that stopped leeching was the "You set your upload to at least 10kb's or we're throttling your download" method. once people hacked the client, people started screaming "The Network is gonna die! DO SOMETHING!!", so other clients including ednkey2000 started implementing Queue Ranking based on upload/download ratio.

Pre QR. You could easily saturate a pipe. I watched someone take a T1 down downloading redhat from it back in 2000. and had the file in less than 15 minutes. Queue's were never a problem and initial start never took longer than 1 hour and only if the file was very rare.

Now. you'd have to wait 2 days for one of the file holders to feel pity on you and start uploading to you and then you might break 20kb's as you upload to people who still need that very part you downloaded. Meanwhile the 900 other holders of the file ignore you because they have the entire file and never download from you, thus denying you to download from them.

And if you're talking about Edonkey2000's Horde, that was a joke. no one outside of edonkey2000 supported it, and by then 90-95% of clients were e-mule based.
--
Frankly, I no longer fear Hell anymore, because I know Satan will just put me in my old office and proceed to unleash an unending barrage of stupidity towards me.

Another problem with Emule is that Emule will keep starting uploads until the average upload is at 2-4kbyteps per upload (unless the uploader uses a mod), so unless a client has few files/no one in queue, you cant download faster than 2-4kbyteps per user, only chance of getting a higher speed is download from other users at same time.