Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Glossary of BitTorrent terms
open-in-new
<h2 id="terms">Terms</h2> <h3>Availability</h3> (Also known as distributed copies.) The availability of each piece in the torrent is defined as the number of peers who have a copy of that piece. The availability of the entire torrent is defined as the nonnegative <a href="/facts/Real_number/R02gw5Pb">real number</a> whose <a href="/facts/Integer_part/ssehyMMf">integer part</a> is the minimum piece availability and whose <a href="/facts/Fractional_part/lSU6Ap1q">fractional part</a> is the fraction of pieces that have higher availability than the minimum piece availability.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> <i>Example:</i> There are 10 pieces, Peer A has pieces 0 to 5, Peer B has 2 to 7, and Peer C has 4 to 9. Pieces 0, 1, 8, 9 have availability 1. Pieces 2, 3, 6, 7 have availability 2. Pieces 4 and 5 have availability 3. The entire torrent has availability 1.6 (1 + 6/10). The integer part is 1 because 1 is the lowest piece availability. The fractional part is 6/10 because more than one peer has pieces 2 to 7 (6 pieces) and there are 10 total pieces. Even though 3 peers have pieces 4 and 5, it does not further increase the availability.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> Sometimes "distributed copies" is considered to be "availability minus 1". So if the availability is 2.6, the distributed copies will be 1.6 because it is only counting the additional "copies" of the file. <h3>Choked</h3> Describes a peer to which the client refuses to send file pieces. A client <i>chokes</i> another client in several situations: <ul><li>The second client is a <i>seed</i>, in which case it does not want any pieces (i.e., it is completely <i>uninterested</i>)</li> <li>The client is already uploading at its full capacity (it has reached the value of max_uploads)</li> <li>The second client has been <a href="/facts/Blacklist_(computing)/ShhQWdCd">blacklisted</a> for being abusive or is using a blacklisted BitTorrent client.</li></ul> <h3>Client</h3> The program that enables <a href="/facts/Peer-to-peer/wCCdPb0H">peer-to-peer</a> <a href="/facts/File_sharing/7GISy0GJ">file sharing</a> via the BitTorrent protocol. See <a href="/facts/Comparison_of_BitTorrent_clients/prxFGlHW">Comparison of BitTorrent clients</a>. <h3>Distributed Hash Table</h3> <a href="/facts/Distributed_hash_table/3eDfAaoh">Distributed Hash Tables</a> (DHT) are used in Bittorrent for peers to send a list of other seeds/peers in the swarm for a particular torrent directly to a client without the need for a tracker. <h3>Endgame / Endgame mode</h3> Any applied algorithm for downloading the last few pieces (see below) of a torrent. In typical client operation the last download pieces arrive more slowly than the others. This is because the faster and more easily accessible pieces should have already been obtained. In order to prevent the last pieces becoming unobtainable, BitTorrent clients attempt to get the last missing pieces from all of its peers. Upon receiving the last pieces a cancel request command is sent to other peers. <h3>Fake</h3> A fake torrent is a torrent that does not contain what is specified in its name or description (e.g. a torrent is said to contain a video, but it contains only a <a href="/facts/Snapshot_(photography)/oAVdaI9V">snapshot</a> of a moment in the video, or in some cases <a href="/facts/Malware/5ee7TLFR">malware</a>). <h3>Freeleech</h3> Freeleech means that the download size of the torrent does not count towards your overall ratio, only the uploaded amount on the torrent counts toward your ratio. <h3>Grab</h3> A torrent is grabbed when its metadata files have been downloaded. <h3>Hash</h3> The <a href="/facts/Hash_function/rk6MlCt3">hash</a> is a digital fingerprint in the form of a string of <a href="/facts/Alphanumeric/ytA9RSIv">alphanumeric</a> characters (typically <a href="/facts/Hexadecimal/02ohQW22">hexadecimal</a>) in the .torrent file that the client uses to verify the data that is being transferred. "Hash" is the shorter form of the word "<a href="/facts/Cryptographic_hash_function/cuxkgbST">hashsum</a>". Torrent files contain information like the file list, sizes, pieces, etc. Every piece received is first checked against the hash. If it fails verification, the data is discarded and requested again. Hash checks greatly reduce the chance that invalid data is incorrectly identified as valid by the BitTorrent client, but it is still possible for invalid data to have the same hash value as the valid data and be treated as such. This is known as a <a href="/facts/Hash_collision/QwAesPFG">hash collision</a>. Torrent and p2p files typically use 160 bit hashes that are reasonably free from hash collision problems, so the probability of bad data being received and passed on is extraordinarily small. <h3>Health</h3> Health is shown in a bar or in % usually next to the torrent's name and size, on the site where the .torrent file is hosted. It shows if all pieces of the torrent are available to download (i.e. 50% means that only half of the torrent is available). Health does not indicate whether the torrent is free of viruses. <h3>Hit-and-run</h3> To intentionally "leech" a file; downloading a file while seeding as little as possible. It's abbreviated HnR or H&R. <h3>Index</h3> <p class="note">Main article: <a href="/facts/BitTorrent_index/HP9ChWWW">BitTorrent index</a></p> An index is a list of .torrent files (usually including descriptions and other information) managed by a <a href="/facts/Website/SAsjJnca">website</a> and available for searches. An <i>index</i> website can also be a <i>tracker</i>. <h3>Interested</h3> Describes a downloader who wishes to obtain pieces of a file the client has. For example, the uploading client would flag a downloading client as 'interested' if that client did not possess a piece that it did, and wished to obtain it. <h3>Leech</h3> <p class="note">Main article: <a href="/facts/Leech_(computing)/J7lxoe4D">Leech (computing)</a></p> <i>Leech</i> has two meanings. Often, <i>leecher</i> is synonymous with <i>downloader</i>: simply describing a <i>peer</i> or any client that does not have 100% of the data. The term <i>leech</i> also refers to a <i>peer</i> (or peers) that has a negative effect on the swarm by having a very poor share ratio, downloading much more than they upload. Leeches may be on asymmetric Internet connections or do not leave their <a href="/facts/BitTorrent_client/prxFGlHW">BitTorrent client</a> open to seed the file after their download has completed. However, some leechers intentionally avoid uploading by using modified clients or excessively limiting their upload speed. <h3>Lurker</h3> <p class="note">Main article: <a href="/facts/Lurker/1xhtVqhX">Lurker</a></p> A <i>lurker</i> is a user that only downloads files from the group but does not add new content. It does not necessarily mean that the lurker will not seed. Not to be confused with a <i>leecher</i>. <h3>Magnet link</h3> A mechanism different from a .torrent metafile which can be used to identify a set of files for BitTorrent based on content, as opposed to referencing any particular tracker. The method is not limited to BitTorrent data. See <a href="/facts/Magnet_URI_scheme/dGRRYeXM">Magnet URI scheme</a>. <h3>Overseeded</h3> In private trackers using ratio credit, a torrent is <i>overseeded</i> when its availability is so high that seeders have difficulty finding downloaders. <h3>p2p</h3> <p class="note">Main article: <a href="/facts/Peer-to-peer/wCCdPb0H">Peer-to-peer</a></p> In a p2p network, each node (or computer on the network) acts as both a client and a server. In other words, each computer is capable of both responding to requests for data and requesting data itself. <h3>Peer</h3> A <i>peer</i> is one instance of a BitTorrent client running on a computer on the <a href="/facts/Internet/Xw1rVvJU">Internet</a> to which other clients connect and transfer data. Depending on context, "peer" can refer either to any client in the swarm or more specifically to a downloader, a client that has only parts of the file. <h3>Piece</h3> This refers to the torrented files being divided up into equal specific sized pieces (<i>e.g.</i>, 64kB, 128kB, 512kB, 1MB, 2MB, 4MB or 8MB). The pieces are distributed in a <a href="/facts/Randomness/QJQBoEX5">random</a> fashion among peers in order to optimize trading efficiency. <h3>Ratio credit</h3> <i>Ratio credit</i>, also known as <i>upload credit</i> or <i>ratio economy</i>, is a currency system used on a number of private trackers to provide an incentive for higher upload/download ratios among member file-sharers. In such a system, those users with greater amounts of bandwidth, hard drive space (particularly <a href="/facts/Seedbox/KPwINTcv">seedboxes</a>) or idle computer <a href="/facts/Uptime/7PXQlwEE">uptime</a> are at a greater advantage to accumulate ratio credits versus those lacking in any one or more of the same resources. <h3>Scraping</h3> <p class="note">Main article: <a href="/facts/Tracker_scrape/MIvox4wP">Tracker scrape</a></p> This is when a client sends a request to the tracking server for information about the statistics of the torrent, such as with whom to share the file and how well those other users are sharing. <h3>Seed / seeding</h3> A <i>seed</i> refers to a machine possessing all of the data (100% completion). A <i>peer</i> or <i>downloader</i> becomes a seed when it completely downloads all the data and continues/starts uploading data for other peers to download from. This includes any <i>peer</i> possessing 100% of the data or a <a href="/facts/BitTorrent/HP9ChWWW">web seed</a>. When a <i>downloader</i> starts uploading content, the peer becomes a <i>seed</i>. <i><a href="/facts/Seeding_(computing)/awv2qFkS">Seeding</a></i> refers to leaving a peer's BitTorrent client open and available for additional individuals to download from. Normally, a peer should seed more data than download. However, whether to seed or not, or how much to seed, depends on the availability of downloaders and the choice of the peer at the seeding end. <h3>Share ratio</h3> A user's <i>share ratio</i> for any individual torrent is a number determined by dividing the amount of data that user has uploaded by the amount of data they have downloaded. Final share ratios over 1.0 carry a positive connotation in the BitTorrent community, because they indicate that the user has sent more data to other users than they received. Likewise, share ratios under 1 have negative connotation. <h3>Snatch</h3> A torrent is <i>snatched</i> when its data files have been downloaded. <h3>Snubbing</h3> An uploading client is displayed as <i>snubbed</i> if the downloading client has not received any data from it in over 60 seconds. <h3>Super-seeding</h3> When a file is new, much time can be wasted because the <a href="/facts/Seeding_(computing)/awv2qFkS">seeding</a> client might send the same file piece to many different peers, while other pieces have not yet been downloaded at all. Some clients, like <a href="/facts/Vuze/4ScuT05P">Vuze</a>, <a href="/facts/%25CE%259CTorrent/NB05H7Ke">μTorrent</a>, and <a href="/facts/QBittorrent/0MmRbbsa">qBittorrent</a> have a "<a href="/facts/Super-seeding/QXR9D4Vv">super-seed</a>" mode, where they try to only send out pieces that have never been sent out before, theoretically making the initial propagation of the file much faster. However the super-seeding becomes less effective and may even reduce performance compared to the normal "rarest first" model in cases where some peers have poor or limited connectivity. This mode is generally used only for a new torrent, or one which must be re-seeded because no other seeds are available. <h3>Swarm</h3> Together, all <i>peers</i> (including <i>seeds</i>) sharing a <i>torrent</i> are called a <i>swarm</i>.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> For example, six ordinary <i>peers</i> and two <i>seeds</i> make a <i>swarm</i> of eight. This is a holdover from the predecessor to BitTorrent, a program called Swarmcast, originally from OpenCola. BitTorrent may sometimes display a swarm number that has no relation to the number of seeds and peers you are connected to or who are available. For example, it may show 5 out of 10 connected peers, 20 out of 100 connected seeds, and a swarm of 3. <h3>Torrent</h3> A <i><a href="/facts/Torrent_file/j0SwIJrW">torrent</a></i> can mean either a .torrent <a href="/facts/Metadata/qt35z79C">metadata</a> file or all files described by it, depending on context. The <i>torrent file</i> contains metadata about all the files it makes downloadable, including their names and sizes and <a href="/facts/Checksum/AqxQ0I8g">checksums</a> of all pieces in the <i>torrent</i>. It also contains the address of a <i>tracker</i> that coordinates communication between the peers in the swarm.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> <h3>Tracker</h3> <p class="note">Main article: <a href="/facts/BitTorrent_tracker/GPz9m4LU">BitTorrent tracker</a></p> A <i>tracker</i> is a server that keeps track of which seeds and peers are in the swarm.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> Clients report information to the tracker periodically and in exchange, receive information about other clients to which they can connect. The tracker is not directly involved in the data transfer and does not have a copy of the file. It only receives information from the client. <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"How is 'availability' calculated in BitTorrent?". Super User. Retrieved 2023-06-30. <a href="https://superuser.com/questions/1087085/how-is-availability-calculated-in-bittorrent" target="_blank">https://superuser.com/questions/1087085/how-is-availability-calculated-in-bittorrent</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"How is 'availability' calculated in BitTorrent?". Super User. Retrieved 2023-06-30. <a href="https://superuser.com/questions/1087085/how-is-availability-calculated-in-bittorrent" target="_blank">https://superuser.com/questions/1087085/how-is-availability-calculated-in-bittorrent</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"BEP-0003: The BitTorrent Protocol Specification". Bittorrent.org. Archived from the original on 2019-07-26. Retrieved 2009-10-22. <a href="http://www.bittorrent.org/beps/bep_0003.html" target="_blank">http://www.bittorrent.org/beps/bep_0003.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"BEP-0003: The BitTorrent Protocol Specification". Bittorrent.org. Archived from the original on 2019-07-26. Retrieved 2009-10-22. <a href="http://www.bittorrent.org/beps/bep_0003.html" target="_blank">http://www.bittorrent.org/beps/bep_0003.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"BEP-0003: The BitTorrent Protocol Specification". Bittorrent.org. Archived from the original on 2019-07-26. Retrieved 2009-10-22. <a href="http://www.bittorrent.org/beps/bep_0003.html" target="_blank">http://www.bittorrent.org/beps/bep_0003.html</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> </ol>