| advertise add site services publishers database health videos | ![]() | about toolbar stats live show health store more stuff JOIN/LOGIN |
BitComet (originally named SimpleBT client from versions 0.11 to 0.37) is a controversial[1] 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]
[edit] FeaturesThe 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 only certain files for download inside a torrent package, NAT traversal,[3] Initial-Seeding (Super-Seeding) and support for Magnet Links. When downloading, BitComet gives you the option to prioritize the first and last portions of media files so that files may be previewed before they are completely downloaded. 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.[5] The software includes an application to play Flash Video files (.flv and .swf files).[6] [edit] Optional standalone softwareBitComet.com offers a BitTorrent tracker available for download from the official site.[7] The FLV player program can also be downloaded separately and used independently of the BitComet software. [edit] Search engineThe search site is google.atcomet.net [edit] Controversy and criticism[edit] Hash reportingSince version 0.86 BitComet includes discussion and stat-tracking features which send information about torrents to the Bitcomet.com servers, including the torrent hash.[8][verification needed] [edit] DHT exploitDuring 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.[9] BitComet developer RnySmile reverted the client back to version 0.59 in response to the blacklisting.[10] The DHT exploit was fixed in version 0.61.[11][12] [edit] Padding filesStarting 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", which has caused problems with partial-torrent downloads in all bittorrent clients. To accomplish this, BitComet fills the remainder of each last "piece" with an empty "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. Other clients could choose to hide these files, as BitComet advises, but they choose not to.[13] Creation of padding files was enabled by default in version 0.85, and disabled by default in version 0.86 onward.[verification needed] [edit] Validity of criticismIn July 2007, Robb Topolski, a self-described “networking and protocol expert”[2] 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.[14] 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.[15] [edit] FileHippo ControversyThe download site FileHippo ceased carrying new versions of BitComet in April 2008, with this announcement.
This occurred after FileHippo reportedly noticed that the design of the AppHit.com site (which among other sites, also hosts for downloading several applications developed by the Comet team) was very similar with the one FileHippo used. However, the BitComet team, which has only a partnership relation with AppHit but it's not involved in any way in the administration or maintenance of the said site, was not aware of this issue and notified the AppHit staff of the situation, as soon as they were made aware of it. Therefore, the reaction of FileHippo seems a bit misguided since they erroneously assumed that AppHit is a site developed by the Comet team. [edit] Torrent file formatAccording to the official BitTorrent specification, 'All strings in a .torrent file that contains text must be UTF-8 encoded'. When generating torrents on (e.g.) Chinese or Japanese (non-Latin character) systems, BitComet encodes the files' names and paths using the Windows Chinese/Japanese code page, and stores a UTF-8 version in a non-standard attribute. BitComet-generated torrents on non-Latin systems therefore violate the official specification, which does not allow encodings other than UTF-8. Since there is no alternative specification to standardise the use of other encodings, other clients may incorporate other solutions, or ignore the problem, and so might not be able to read each others' file names correctly. [17] [18] [edit] See also
[edit] References
[edit] External links
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| ↑ top of page ↑ | about thumbshots |