the forums at degreez.net

It is currently Thu Aug 06, 2020 9:51 am

All times are UTC - 7 hours [ DST ]




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
PostPosted: Sun Dec 18, 2005 12:49 pm 
Anonymous wrote:
bitcomet is not a leech client it is a bt cliient like any other client minus superseeding
Allow me to correct you:

BitComet does not follow the BitTorrent protocol. In some places it violates only the 'spirit' (the purpose) of parts of the protocol, but for others it violates it by any reasonable measure. It does this to get a far bigger piece of the bandwidth pie in a torrent at the expense of others in the torrent and even the continuation of the torrent. Therefore, it is merely a leech program trying to masquarade as a "true" BitTorrent client.
Anonymous wrote:
how can we complain about something that is free?
The issue is not whether BitComet is free, the issue is it cheats others.

It sabotages super-seeds and drains the torrent bandwidth:
http://azureus.aelitis.com/wiki/index.php/Super_Seeding
Comment: BitComet interferes with SuperSeeding?

...it disobeys the private torrent flag:
http://www.p2pforums.com/viewtopic.php?t=17442
[BUG] DHT connecting on private torrents
(Note: This is BitComet's forums -- where you'd expect the most denials of problems...but even its supporters admitted this is a problem and understandable that private trackers needed to ban it.)

...it excessively reconnects to the tracker to get as many seed and peer connections as possible. This has overloaded many trackers, knocking some offline for hours. ...Which might explain many of the tracker errors people post about here.
(I only have anecdotal evidence on that, and no URL for this yet.)

...it does basically the same to individual peers+seeds in a torrent:
http://forum.utorrent.com/viewtopic.php?id=3531&p=1
mrbraindead: "I tested on open torrent trackers today, and on some trackers (I think they just are fast enough) BitComet users connect 5 - 10 times per SECOND to my utorrent client(shown in log).
Every BitCoemt client does so, while no other client connects more than 2 times in 10 minutes."
(Personally, I've heard of slower Denial-of-Service attacks.)

And it is easily configured to be even more leechlike than that! It allows you to (try to) download 15+ torrents at a time with multiple uploads for each, with a TOTAL upload speed of 1 KB/sec. Meaning EACH upload might average 0.02 KB/sec...over many hours. That's actually WORSE than uploading nothing due to the overhead costs for each connection! Btw, you'd get faster download speeds using a higher upload speed -- but if you're just looking to sabotage torrents, you won't care about speeds.

There is even some anecdotal evidence that this VERY slow upload rate also causes additional failed hashes on file chunks due to lost or corrupted packets, even 5-20% of ALL the file chunks of a torrent! This means everyone with this problem has to download+upload 5-20% more than the total length of the file. I don't see how that is beneficial for anyone.
(I don't have a URL to this one either, though I've read multiple people commenting that they've seen this -- often when they use BitComet!)

...And I remember thinking 3 KB/sec upload speed and 2 uploads at once (which is 1.5 KB/sec each) on BitTornado was slow!


Top
  
 
 Post subject:
PostPosted: Sun Dec 18, 2005 7:02 pm 
Offline

Joined: Sun Mar 07, 2004 10:05 am
Posts: 1212
Patch made to prevent this sort of exploitation; expect it in the next release.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 7 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group