BitComet

BitComet
Developer(s)BitComet Development Group (China)[1]
Initial releaseAugust 6, 2003; 21 years ago (2003-08-06)
Stable release(s)
Windows2.10[2] Edit this on Wikidata / 9 October 2024; 44 days ago (9 October 2024)
macOS2.10[2] Edit this on Wikidata / 9 October 2024; 44 days ago (9 October 2024)
Preview release(s) [±]
None (n/a) [±]
Written inC++[citation needed]
Operating systemWindows 2000 and later, Android,[3] macOS
Available in52 languages[4]
TypeBitTorrent client
LicenseAdware
Websitewww.bitcomet.com/en Edit this on Wikidata

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.[5] Its first public release was version 0.28. The current BitComet logo has been used since version 0.50.[6]

Features

[edit]

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),[7] 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),[8] 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.[9] 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.[7]

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.[10]

BitComet FLV Player version 1.3

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

In February 2011, BitComet launched an 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.[12]

Optional standalone software

[edit]

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

Search engine

[edit]

The search site is google.atcomet.com

Controversy and criticism

[edit]

Hash reporting

[edit]

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.[citation needed]

DHT exploit

[edit]

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.[14] BitComet developer RnySmile reverted the client back to version 0.59 in response to the blacklisting.[15]

The DHT exploit was fixed in version 0.61.[16][17]

Padding files

[edit]

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.[18] 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" [19]

Creation of padding files has been enabled by default since version 0.85, and as of version 1.36 is still enabled by default.[citation needed]

FileHippo controversy

[edit]

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.[20]

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

[edit]

According to the official BitTorrent specification, 'All strings in a .torrent file that contains text must be UTF-8 encoded'.[21] When generating torrents on non-Latin character systems such as Chinese or Japanese, BitComet versions prior to 1.20[22] encoded the files' names and paths using the Windows Chinese/Japanese code page, and stored a UTF-8 version in a non-standard attribute.[23] Starting with the March 2010 release of version 1.20, BitComet's torrent format now conforms to the standard.

See also

[edit]

References

[edit]
  1. ^ "BitComet Development Group Private Company Information". Bloomberg Businessweek. Archived from the original on 13 December 2019. Retrieved 14 April 2014.
  2. ^ a b https://www.bitcomet.com/en/changelog. {{cite web}}: Missing or empty |title= (help)
  3. ^ "BitComet". Google Play Store. Archived from the original on 2021-10-31. Retrieved 2020-12-10.
  4. ^ "Help_translations_of_bitcomet [BitComet Wiki]". Archived from the original on 2010-03-05. Retrieved 2010-02-26.
  5. ^ "Supported Languages in BitComet". 2009-03-11. Archived from the original on 2015-12-11. Retrieved 2008-05-13.
  6. ^ "BitComet BitTorrent Client". 2006-05-10. Archived from the original on 2008-05-13. Retrieved 2008-05-13.
  7. ^ a b "What is NAT Traversal in BitComet??". 2009-11-24. Archived from the original on 2019-08-18. Retrieved 2010-02-23.
  8. ^ "PEX in BitComet". 2010-02-21. Archived from the original on 2010-12-17. Retrieved 2010-02-23.
  9. ^ "Torrent Share and Torrent Exchange". 2010-01-01. Archived from the original on 2013-10-05. Retrieved 2010-01-01.
  10. ^ "eMule Plugin for BitComet". 2008-03-27. Archived from the original on 2008-05-13. Retrieved 2008-05-13.
  11. ^ "BitComet FLV Player (Flash Video Player)". 2008-03-27. Archived from the original on 2008-05-13. Retrieved 2008-05-13.
  12. ^ "BitComet Adds Support for "Anonymous" Downloads – TorrentFreak". TorrentFreak. 2011-06-02. Archived from the original on 2018-04-05. Retrieved 2018-04-05.
  13. ^ "BitComet Tracker". 2008-03-27. Archived from the original on 2008-04-30. Retrieved 2008-05-13.
  14. ^ Thomas Mennecke (2005). "BitComet Banned". Archived from the original on 2007-01-24. Retrieved 2007-01-15.
  15. ^ Thomas Mennecke (2005). "BitComet Reverts to Version .59". Archived from the original on 2007-01-24. Retrieved 2007-01-15.
  16. ^ Thomas Mennecke (2006). "BitComet .62 and You". Archived from the original on 2007-05-18. Retrieved 2006-12-03.
  17. ^ Thomas Mennecke (2006). "BitComet .64 Released". Archived from the original on 2007-10-08. Retrieved 2006-01-15.
  18. ^ Ernesto (2007-08-23). "BitComet Pollutes BitTorrent with Junk Data". TorrentFreak. Archived from the original on 2007-08-24. Retrieved August 24, 2007.
  19. ^ "align_file_to_piece_boundary [BitComet Wiki]". Archived from the original on May 12, 2015. Retrieved May 13, 2015.
  20. ^ "Download BitComet 0.99 – FileHippo.com". April 2008. Archived from the original on 2008-04-20. Retrieved 2009-12-18.
  21. ^ Bram Cohen. "The BitTorrent Protocol Specification". Archived from the original on 2014-02-08. Retrieved 2009-08-26.
  22. ^ BitComet. "BitComet release notes". Archived from the original on 2010-12-17. Retrieved 2010-03-27. Core Improve: use UTF-8 encoding when making torrent file by default for all language versions of Windows.
  23. ^ BitComet Support Team. "BitComet – Torrent File Format". Archived from the original on 2009-05-14. 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.
[edit]