Tracker scrape

Last updated

A scrape, or tracker scrape, is a request sent by a BitTorrent client to a tracker. A request is sent, connection to the tracker is established, information is exchanged, then the connection is closed. The request does something like a "wipe" or a "pass" over the tracker, and then the tracker sends information back to the client. [1] [2]

A BitTorrent tracker is a special type of server that assists in the communication between peers using the BitTorrent protocol. In peer-to-peer file sharing, a software client on an end-user PC requests a file, and portions of the requested file residing on peer machines are sent to the client, and then reassembled into a full copy of the requested file. The "tracker" server keeps track of where file copies reside on peer machines, which ones are available at time of the client request, and helps coordinate efficient transmission and reassembly of the copied file. Clients that have already begun downloading a file communicate with the tracker periodically to negotiate faster file transfer with new peers, and provide network performance statistics; however, after the initial peer-to-peer file download is started, peer-to-peer communication can continue without the connection to a tracker. Since the creation of the distributed hash table (DHT) method for "Trackerless" torrents, BitTorrent trackers have largely become redundant; however, they are still often included with torrents to improve the speed of peer discovery.

The returned information can contain such information as, whether the tracker is on- or offline, the reason it is offline, the numbers of peers and seeds (sending a list of all peers in the swarm is usually much more bandwidth consuming than just sending a scrape result), etc. Note that some trackers don't support scrape requests, but it is still possible to use the tracker as usual.

A client scrapes in order to determine whether or not to send an announce requesting more peers. Sending a scrape result usually requires less data transfer than sending a list of peers.

Clients with scrape support will scrape the tracker many times during the course of a download to update its information about the swarm. The tracker is scraped many thousands of times for each torrent alone, even if the swarm is not very big. The tracker can usually handle this number of requests. However, if there are more requests than strictly necessary, this can destabilize the tracker and put it offline.

Related Research Articles

Gnutella is a large peer-to-peer network. It was the first decentralized peer-to-peer network of its kind, leading to other, later networks adopting the model. It celebrated a decade of existence on March 14, 2010, and has a user base in the millions for peer-to-peer file sharing.

An anonymous P2P communication system is a peer-to-peer distributed application in which the nodes, which are used to share resources, or participants are anonymous or pseudonymous. Anonymity of participants is usually achieved by special routing overlay networks that hide the physical location of each node from other participants.

The Invisible Internet Project (I2P) is an anonymous network layer that allows for censorship-resistant, peer to peer communication. Anonymous connections are achieved by encrypting the user's traffic, and sending it through a volunteer-run network of roughly 55,000 computers distributed around the world. Given the high number of possible paths the traffic can transit, a third party watching a full connection is unlikely. The software that implements this layer is called an "I2P router", and a computer running I2P is called an "I2P node". I2P is free and open source, and is published under multiple licenses.

BitComet BitTorrent Client for Microsoft Windows

BitComet 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.

In file sharing, super-seeding is an algorithm developed by John Hoffman for the BitTorrent communications protocol that helps downloaders to be able to become uploaders more quickly, but it introduces the danger of total seeding failure if there is only one downloader.

Transmission (BitTorrent client) BitTorrent client

Transmission is a BitTorrent client which features a variety of user interfaces on top of a cross-platform back-end. Transmission is free software licensed under the terms of the GNU General Public License, with parts under the MIT License.

The UDP tracker protocol is a high-performance low-overhead BitTorrent tracker protocol. It uses the stateless User Datagram Protocol (UDP) for data transmission instead of the HTTP protocol regular trackers use. The data is in a custom binary format instead of the standard bencode algorithm BitTorrent uses for most communication.

Protocol encryption (PE), message stream encryption (MSE) or protocol header encrypt (PHE) are related features of some peer-to-peer file-sharing clients, including BitTorrent clients. They attempt to enhance privacy and confidentiality. In addition, they attempt to make traffic harder to identify by third parties including internet service providers (ISPs).

Peer exchange or PEX is a communications protocol that augments the BitTorrent file sharing protocol. It allows a group of users that are collaborating to share a given file to do so more swiftly and efficiently.

Vuze

Vuze is a BitTorrent client used to transfer files via the BitTorrent protocol. Vuze is written in Java, and uses the Azureus Engine. In addition to downloading data linked to .torrent files, Azureus allows users to view, publish and share original DVD and HD quality video content. Content is presented through channels and categories containing TV shows, music videos, movies, video games, series and others. Additionally, if users prefer to publish their original content, they may earn money from it.

The following is a general comparison of BitTorrent clients, which are computer programs designed for peer-to-peer file sharing using the BitTorrent protocol.

This is a glossary of jargon related to peer-to-peer file sharing via the BitTorrent protocol.

P4P, or proactive network provider participation for P2P, is a method for internet service providers (ISPs) and peer-to-peer (P2P) software to optimize peer-to-peer connections. P4P proponents say that it can save an ISP significant costs, and that using local connections also speeds up download times for P2P downloaders by 45%, critics say that this will favor downloaders on some ISPs but come at the expense of others.

libtorrent is an open-source implementation of the BitTorrent protocol. It is written in and has its main library interface in C++. Its most notable features are support for Mainline DHT, IPv6, HTTP seeds and µTorrent's peer exchange. libtorrent uses Boost, specifically Boost.Asio to gain its platform independence. It is known to build on Windows and most Unix-like operating systems.

In the BitTorrent file distribution system, a torrent file or METAINFO is a computer file that contains metadata about files and folders to be distributed, and usually also a list of the network locations of trackers, which are computers that help participants in the system find each other and form efficient distribution groups called swarms. A torrent file does not contain the content to be distributed; it only contains information about those files, such as their names, sizes, folder structure, and cryptographic hash values for verifying file integrity. The term torrent may refer either to the metadata file or to the files downloaded, depending on the context.

TopBT

TopBT, is a topology-aware BitTorrent client implemented with open-source Vuze code base Version 4.0.0.4. It is developed as a research result from The Ohio State University. The "Top" in its name stands for "Topology" and it refers to the program's network topology-awareness feature. it actively discovers its network proximities to its connected peers by actively sending packets to those peers, and inspecting their responses. Through topology-awareness, TopBT aims to reduce unnecessary network traffic and at the same time, on average maintain its download speed. The paper "TopBT: a topology-aware and infrastructure-independent BitTorrent client" describes how it works.

Mainline DHT is the name given to the Kademlia-based Distributed Hash Table (DHT) used by BitTorrent clients to find peers via the BitTorrent protocol. The idea of utilizing a DHT for distributed tracking was first implemented in Azureus 2.3.0.0 in May 2005, from which it gained significant popularity. Unrelated but similarly timed BitTorrent, Inc. released their own similar DHT into their client, called Mainline DHT and thus popularized the use of distributed tracking in the BitTorrent Protocol. Measurement shows by 2013 users of Mainline DHT is from 10 million to 25 million, with a daily churn of at least 10 million.

WebTorrent peer-to-peer web-based torrent client

WebTorrent is a peer-to-peer (P2P) streaming torrent client written completely in JavaScript by Feross Aboukhadijeh, John Hiesey, and the team at WebTorrent and on GitHub, for use in web browsers, as well as a WebTorrent Desktop stand alone version able to bridge WebTorrent and BitTorrent serverless networks.

References

  1. "Vuze Wiki: Scrape". Vuze. 2012-01-12. Retrieved 2018-07-27.
  2. "Bittorrent Protocol Specification v1.0: Tracker 'scrape' Convention". 2017-02-01. Retrieved 2018-07-27.