BitComet client version 1.40 running on Windows 10
|Developer(s)||BitComet Development Group (China)|
|Initial release||August 6, 2003|
|Stable release||1.57 (May 8, 2019[±])|
|Preview release||None (n/a) [±]|
|Written in||C++|
|Operating system||Windows 2000 and later|
|Available in||52 languages|
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. Its first public release was version 0.28. The current BitComet logo has been used since version 0.50.
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 main features include an embedded Internet Explorer window to let users search for torrents. 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 (removed in v.1.03), Peer Exchange (in older versions, using a proprietary protocol and starting with v.1.19 also by using the Extension Protocol, implementing a PEX mechanism compatible with µTorrent / Mainline PEX), Initial-Seeding (Super-Seeding) and support for Magnet Links.
When downloading, BitComet provides the option to prioritize the first and last portions of media files so that files may be previewed before they are completely downloaded.
It also has a "Preview Download Mode" in which all pieces of the torrent will be, basically, downloaded sequentially thus allowing the user to play a media file while downloading (provided that the downloading speed and piece availability stay ahead of playing bitrate).
BitComet also allows users to share their .torrent files, on a searchable P2P network, with other BitComet users through the torrent sharing feature, named "Torrent Share" in previous versions and renamed to "Torrent Exchange" since v.1.17. 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.
In February 2011, BitComet launched anonymous downloading feature to its VIP customers. Using this feature, downloads will be handled by BitComet VIP servers and the real IP address of the user will be hidden.
Optional standalone software
The search site is google.atcomet.com
Controversy and criticism
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 ignore 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. BitComet developer RnySmile reverted the client back to version 0.59 in response to the blacklisting.
Starting with version 0.85 (from early 2007), BitComet added a non-standard option to its torrent maker that ensures that no two data files in a multi-file torrent occupy the same BitTorrent "piece." To accomplish this, BitComet includes in the torrent a collection of empty "padding" files which houses the remainder of each file's last "piece". While these files are transparent to BitComet users, they damage the performance of other clients, because peers must devote resources and bandwidth to the padding files, with no benefit to the non-BitComet users. These files can constitute up to 10% of the total data transferred, creating a substantial drain on the swarm. BitComet developers added this feature to allow support of a feature called Long-Term Seeding in which the BitComet client can download files from other BitComet clients who have an identical file but not from the same torrent. It also allows the downloading of individual files from other non torrent sources like ED2K links. The addition of the padding file ensures that a complete version of the file can be obtained rather than being unable to complete the relevant file or last "piece" 
Creation of padding files has been enabled by default since version 0.85, and as of version 1.36 is still enabled by default.[verification needed]
Validity of criticism
In July 2007, Robb Topolski, a self-described “networking and protocol expert” 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.
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.
The download site FileHippo ceased carrying new versions of BitComet in April 2008, with this announcement.
As of April 2008 FileHippo will no longer be updating BitComet. As they have copied the FileHippo site text, files, images and update checker and are passing it off as original work. We recommend you use a different more reputable torrent client such as uTorrent.
This occurred after FileHippo reportedly noticed that the design and code of the AppHit.com site was very similar with the one FileHippo used, copying not only icons, but text from FileHippo's website and FileHippo's own original update checking software.
Because AppHit and BitComet were contractual partners, FileHippo decided to stop carrying BitComet. BitComet has since terminated the partnership, by 2015 FileHippo made BitComet available once more.
Torrent file format
According to the official BitTorrent specification, 'All strings in a .torrent file that contains text must be UTF-8 encoded'. When generating torrents on non-Latin character systems such as Chinese or Japanese, BitComet versions prior to 1.20 encoded the files' names and paths using the Windows Chinese/Japanese code page, and stored a UTF-8 version in a non-standard attribute. Starting with the March 2010 release of version 1.20, BitComet's torrent format now conforms to the standard.
- "BitComet Development Group Private Company Information". Bloomberg Businessweek. Retrieved 14 April 2014.
- "BitComet Changelog". www.bitcomet.com. 2018-06-12. Retrieved 2018-06-17.
- "Supported Languages in BitComet". 2009-03-11. Retrieved 2008-05-13.
- "BitComet BitTorrent Client". 2006-05-10. Archived from the original on 2008-05-13. Retrieved 2008-05-13.
- "What is NAT Traversal in BitComet??". 2009-11-24. Retrieved 2010-02-23.
- "PEX in BitComet". 2010-02-21. Retrieved 2010-02-23.
- "Torrent Share and Torrent Exchange". 2010-01-01. Retrieved 2010-01-01.
- "eMule Plugin for BitComet". 2008-03-27. Retrieved 2008-05-13.
- "BitComet FLV Player (Flash Video Player)". 2008-03-27. Retrieved 2008-05-13.
- "BitComet Adds Support for "Anonymous" Downloads - TorrentFreak". TorrentFreak. 2011-06-02. Retrieved 2018-04-05.
- "BitComet Tracker". 2008-03-27. Retrieved 2008-05-13.
- BitComet.com (2008). "BitComet reporting bug?". Retrieved 2008-05-15.
- Thomas Mennecke (2005). "BitComet Banned". Retrieved 2007-01-15.
- Thomas Mennecke (2005). "BitComet Reverts to Version .59". Retrieved 2007-01-15.
- Thomas Mennecke (2006). "BitComet .62 and You". Retrieved 2006-12-03.
- Thomas Mennecke (2006). "BitComet .64 Released". Retrieved 2006-01-15.
- Ernesto (2007-08-23). "BitComet Pollutes BitTorrent with Junk Data". TorrentFreak. Retrieved August 24, 2007.
- "align_file_to_piece_boundary [BitComet Wiki]". Retrieved May 13, 2015.
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.
- 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.”
- "Download BitComet 0.99 - FileHippo.com". April 2008. Retrieved 2009-12-18.
- Bram Cohen. "The BitTorrent Protocol Specification". Retrieved 2009-08-26.
BitComet. "BitComet release notes". Retrieved 2010-03-27.
Core Improve: use UTF-8 encoding when making torrent file by default for all language versions of Windows.
BitComet Support Team. "BitComet - Torrent File Format". Retrieved 2009-08-26.
In BitComet v0.58 or before, the string is encoded using MSCB (user's code page), and a ".utf-8" key is added for UTF-8 encoded string. In v0.59, the default encoding is changed to UTF-8 if the user's code page is neither Chinese nor Japanese.