Jump to content

BitComet: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
No edit summary
Tag: references removed
→‎Awards: these are all bullshit awards
Line 180: Line 180:


The one claim he verified as partially correct was that, "BitComet is a poor peer due to no upload slot control; upload bandwidth is stretched too thin". Topolski's tests indicated that BitComet does lack upload slot control, but only when BitComet is ''initially'' seeding a torrent—that is, when BitComet is the only seeding peer in a swarm, it tends to seed less efficiently than the two other clients he tested. Topolski asserts that when BitComet is ''not'' the only seeding peer in the swarm, or when it is a ''non-seeding'' peer, upload slot control is managed exceptionally well.<ref>Topoloski. “If the BitComet user is the initial seeder, that user will take more time and bandwidth to seed a torrent than any other BitTorrent client I have ever used. (Tests: BitComet 200% to 255%, MainLine 145% to 175%, uTorrent with Super-Seeding 105% to 115%). However, when BitComet is a non-seeding peer, it has exceptionally intelligent slot control. BitComet adjusts the speed of each upload slot individually, providing more upload bandwidth to peers that reciprocate with more upload bandwidth of their own. ... BitComet is an exceptionally poor upload client and should be avoided if the user will be the initial uploader to a swarm. ... This is not an issue if the BitComet user is a seeder in an already-seeded swarm.”</ref>
The one claim he verified as partially correct was that, "BitComet is a poor peer due to no upload slot control; upload bandwidth is stretched too thin". Topolski's tests indicated that BitComet does lack upload slot control, but only when BitComet is ''initially'' seeding a torrent—that is, when BitComet is the only seeding peer in a swarm, it tends to seed less efficiently than the two other clients he tested. Topolski asserts that when BitComet is ''not'' the only seeding peer in the swarm, or when it is a ''non-seeding'' peer, upload slot control is managed exceptionally well.<ref>Topoloski. “If the BitComet user is the initial seeder, that user will take more time and bandwidth to seed a torrent than any other BitTorrent client I have ever used. (Tests: BitComet 200% to 255%, MainLine 145% to 175%, uTorrent with Super-Seeding 105% to 115%). However, when BitComet is a non-seeding peer, it has exceptionally intelligent slot control. BitComet adjusts the speed of each upload slot individually, providing more upload bandwidth to peers that reciprocate with more upload bandwidth of their own. ... BitComet is an exceptionally poor upload client and should be avoided if the user will be the initial uploader to a swarm. ... This is not an issue if the BitComet user is a seeder in an already-seeded swarm.”</ref>

==Awards==
* Softonic featured program
* Softonic rating: excelent (4.5/5)
* Brothersoft.com editor's pick
* Download3K clean award
* Download3k pick award (5/5)
* Software.informer.com: Most downloaded award <ref>http://bitcomet.software.informer.com/awards/</ref>
* Soft32.com Editor's Review Award: Excelent (5/5)
* Soft32.com 100% clean award
* Soft32.com Editor's Pick
* topshareware.com clean award
* Tucows.com: 4/5


==References==
==References==

Revision as of 15:14, 16 May 2009

BitComet
Developer(s)BitComet Development Group
Initial releaseAugust 6, 2003
Stable release
1.10 / March 9, 2009; 15 years ago (2009-03-09)
Preview releaseNone (n/a) [±]
Written inC++
Operating systemWindows 98/Me/2000/XP/2003/Vista
Available in52 languages
TypeBitTorrent client
LicenseProprietary freeware
Websitehttp://www.bitcomet.com

BitComet (originally named SimpleBT client from versions 0.11 to 0.37) is a cross-protocol BitTorrent, HTTP and FTP client written in C++ for Microsoft Windows and available in 52 different languages.[1] Its first public release was version 0.28. The current BitComet logo has been used since version 0.50.[2]

Features

The BitComet program is a multi-threaded multi-protocol hybrid download manager and BitTorrent Peer-to-peer (P2P) file-sharing application. It supports simultaneous download tasks. To complete a particular download, it can draw parts of files from many sources across different P2P and Client-server protocols.

BitComet's chief features include an embedded Internet Explorer window for the purpose of allowing users to search for torrents within the program. Along with the features typical of contemporary BitTorrent clients, it supports UPnP gateway configuration, bandwidth scheduling, Webseeding, selecting downloads inside a torrent package, and NAT traversal.[3]

When downloading, BitComet prioritizes the first and last portions of media files so that files may be previewed before they are completely downloaded. BitComet also allows users to share their torrent files on a searchable P2P network. BitComet uses the Kademlia (mainline) DHT to operate even when the tracker is offline. BitComet is capable of downloading files over HTTP and FTP as well as bittorrent, and it includes download plugins for Firefox, Internet Explorer, and Maxthon.[3]

An optional plugin is available to connect to the eD2K network. The plugin is a modified version of the GPL eMule program. When installed, it connects automatically to a server.[4]

BitComet FLV Player version 1.3

The software includes an application to play Flash Video files (.flv and .swf files).[5]

Optional standalone software

BitComet.com offers a BitTorrent tracker available for download from the official site.[6] The FLV player program can also be downloaded separately and used independently of the BitComet software.

Controversy and criticism

Hash reporting

Since version 0.86 BitComet includes discussion and stat-tracking features which send information about torrents to the Bitcomet.com servers, including the torrent hash.[7][verification needed]

Adware

The official BitComet website claims that "BitComet does not contain any adware or spyware".[8] However, versions 0.85 to 0.97 contained advertising.[9] The current versions no longer contain advertising, except in the web-based search window.[10][verification needed]

DHT exploit

During version 0.60, BitComet received bad publicity because its implementation of the DHT feature, which was new at the time, could be exploited to not respect the private flag of a tracker. This allowed users to avoid download and upload ratio restrictions, which are common on private trackers. Some private trackers responded to this by blacklisting version 0.60.[11] BitComet developer RnySmile reverted the client back to version 0.59 in response to the blacklisting.[12]

The DHT exploit was fixed in version 0.61.[13][14]

Super-seeding

In early 2007, John Hoffman, the creator of super-seeding and author of the BitTornado client, harshly criticized BitComet for using abusive tactics to "game" and "cheat" super-seeding at the expense of other peers: "Since BitComet has proven itself to be a harmful codebase, and since they have forced me to take steps I’d rather not have, I will also be banning connections from that client to my own client and tracker codebases."[15]

Padding files

Starting with version 0.85 (Early 2007), BitComet added an option to its torrent maker that ensures that no two data files in a multi-file torrent occupy the same BitTorrent "piece." This helps enable BitComet to download different parts of a multi-file torrent from non-BitTorrent sources such as http/ftp servers or the ED2K network. To accomplish this, BitComet fills the remainder of each last "piece" with an intervening padding file. While these small and harmless files are transparent to the BitComet user, they can be an annoyance to users of other clients who must deal with them both during and after the download.[16] Creation of padding files was enabled by default in version 0.85, and disabled by default in version 0.86 onward.[verification needed]

Validity of criticism

In July of 2007, Robb Topolski conducted an independent analysis of most accusations leveled against BitComet including the DHT Exploit and Super-seeding controversies mentioned above. He found all but one of the claims to be false or unverifiable. He found that BitComet is not detrimental or malicious to the download or upload speeds of a BitTorrent swarm or the tracker.[17]

The one claim he verified as partially correct was that, "BitComet is a poor peer due to no upload slot control; upload bandwidth is stretched too thin". Topolski's tests indicated that BitComet does lack upload slot control, but only when BitComet is initially seeding a torrent—that is, when BitComet is the only seeding peer in a swarm, it tends to seed less efficiently than the two other clients he tested. Topolski asserts that when BitComet is not the only seeding peer in the swarm, or when it is a non-seeding peer, upload slot control is managed exceptionally well.[18]

References

  1. ^ "Supported Languages in BitComet". 2009-03-11. Retrieved 2008-05-13.
  2. ^ "BitComet BitTorrent Client". 2006-05-10. Retrieved 2008-05-13.
  3. ^ a b "What is BitComet?". 2008-05-07. Retrieved 2008-05-13.
  4. ^ "eMule Plugin for BitComet". 2008-03-27. Retrieved 2008-05-13.
  5. ^ "BitComet FLV Player (Flash Video Player)". 2008-03-27. Retrieved 2008-05-13.
  6. ^ "BitComet Tracker". 2008-03-27. Retrieved 2008-05-13.
  7. ^ BitComet.com (2008). "BitComet reporting bug?". Retrieved 2008-05-15.
  8. ^ BitComet Team (2006). "Official Website". Retrieved 2007-04-19.
  9. ^ Sniperfx70 (2007). "ADDS". Retrieved 2008-01-01.{{cite web}}: CS1 maint: numeric names: authors list (link)
  10. ^ BitComet Team (2008). "No advertisements in current versions". Retrieved 2008-02-10.
  11. ^ Thomas Mennecke (2005). "BitComet Banned". Retrieved 2007-01-15.
  12. ^ Thomas Mennecke (2005). "BitComet Reverts to Version .59". Retrieved 2007-01-15.
  13. ^ Thomas Mennecke (2006). "BitComet .62 and You". Retrieved 2006-12-03.
  14. ^ Thomas Mennecke (2006). "BitComet .64 Released". Retrieved 2006-01-15.
  15. ^ TorrentFreak.com (2007). "BitTornado Bans All BitComet Users". Retrieved 2007-01-07.
  16. ^ Ernesto (2007-08-23). "BitComet Pollutes BitTorrent with Junk Data". TorrentFreak. Retrieved August 24. {{cite web}}: Check date values in: |accessdate= (help); Unknown parameter |accessyear= ignored (|access-date= suggested) (help); Unknown parameter |month= ignored (help)
  17. ^ Rob Topolski (2007-08-02). "STUDY: 'Examining the Myths and Facts Concerning BitComet Behavior'". ZeroPaid. Retrieved 2008-02-07. [Regarding the claim that] BitComet seems to favor uploading to other BitComet clients, even when getting faster download speeds from other clients ... In dozens of observed sessions using BitComet, I see no such preference being given to BitComet peers. ... BitComet is a worthy download client, providing some advantageous features not found in any other current BitTorrent client. Some of these features are confusing and are poorly implemented, but they are not detrimental to a BitTorrent swarm, nor do they take unfair advantage. {{cite web}}: Unknown parameter |month= ignored (help)
  18. ^ Topoloski. “If the BitComet user is the initial seeder, that user will take more time and bandwidth to seed a torrent than any other BitTorrent client I have ever used. (Tests: BitComet 200% to 255%, MainLine 145% to 175%, uTorrent with Super-Seeding 105% to 115%). However, when BitComet is a non-seeding peer, it has exceptionally intelligent slot control. BitComet adjusts the speed of each upload slot individually, providing more upload bandwidth to peers that reciprocate with more upload bandwidth of their own. ... BitComet is an exceptionally poor upload client and should be avoided if the user will be the initial uploader to a swarm. ... This is not an issue if the BitComet user is a seeder in an already-seeded swarm.”

See also

Retrieved from "https://en.wikipedia.org/w/index.php?title=BitComet&oldid=290325610"