2024 XMAS FREELEECH BEGINS!

On behalf of the Staff Team we wish you all a safe and Merry Christmas and a Happy New Year.

Many thanks go out to every member of BT, the Staff Team, our amazing team of Cappers as well as the dedicated support of all BT's Donors, without all you guys BT wouldn't be possible.

Freeleech has now begun and will close around mid January with an announcement to be made a week prior to ending. Please remember that H&R is and always will remain active for all Freeleech torrents.

Enjoy!

No seeding same torrent twice on same IP

Better late than never they said!

Quick message guys with some important information. Several members have been detected seeding the same torrent twice for multiple torrents. Whilst we do permit seeding the same torrent twice at different locations and IP addresses, it is NOT permitted to seed the same torrent twice from the same IP address under any circumstances.

The below message was sent out to all offenders and they were immediately dropped from the peers list. Generally we would not take these measures however the offenders clients decided they would ignore the trackers directive to stop their clients. A good reminder to follow BitTorrent protocol and not to set your client to ignore the trackers commands.

Read the below message that was sent out to recent offenders so that the next time this occurs, it does not occur to you. There is no need to seed twice from the same IP, it has no benefit to you or the tracker and in fact has a few negatives which are listed in the PM below.

Thank you for your time.

=======================

The tracker has identified your account and IP address is seeding the same torrent twice on 30 torrents in total.

1. Swarm Collisions

Redundancy of Peers: When the same user is seeding the same torrent twice, the tracker and other peers may identify multiple sources from the same IP address but with the same content. This can lead to unnecessary redundancy in the swarm, as the same data might be available from the same machine or IP multiple times.

Increased Load on the Tracker: The tracker might count two separate sources as two different peers, increasing the number of peers unnecessarily. This can cause the tracker to manage a larger number of peers than necessary, which can increase the load on the tracker.

Reduced Peer Diversity: The swarm becomes less diverse in terms of IP addresses and geographical locations, reducing the overall robustness of the swarm. More diversity helps improve download speeds by offering more download sources from different locations.

2. Impact on Bandwidth Efficiency

Inefficient Bandwidth Use: If two seeds come from the same location (especially the same machine or a NAT gateway), the overall bandwidth usage may not improve significantly.
Other peers in the swarm may already be receiving data from the initial seed, so seeding the same content again won't provide much benefit and could waste bandwidth.

Unnecessary Data Redundancy: Other peers may have to receive the same pieces of data twice, which might not be necessary if the same machine is already seeding the data.

3. Tracker Overhead

Database Overload: The tracker may store redundant data regarding the same machine, leading to unnecessary database entries or increased overhead for managing these connections. This could impact the performance of the tracker, especially with larger user bases.

Peer Information Inaccuracy: With multiple entries for the same peer, the tracker may display inaccurate or confusing information to other peers, making it harder to see the real number of unique peers.

4. Possible Abuse and Cheating Detection

Cheating Detection Systems: Many trackers use algorithms or scripts to detect cheating, such as users seeding the same torrent multiple times to artificially inflate their upload stats. Seeding the same torrent multiple times from the same IP could trigger these detection systems, leading to penalties like warnings or bans.

Misleading Upload Stats: For systems that track the ratio of uploads and downloads, seeding the same torrent twice from the same location might artificially inflate the user's upload count without actually contributing to the overall health of the swarm, leading to inaccurate data and unfair advantage in ratio-based tracking.

5. Reduced Swarm Health

Less Effective Contribution to the Swarm: Having multiple seeds from the same user (same machine/IP) doesn't contribute to the swarm as effectively as having a spread-out distribution of peers. Ideally, more peers from different locations contribute to faster and more reliable downloading for others.

Peer Isolation: If the majority of peers for a torrent are coming from one IP or location, others might face slower speeds or even find themselves isolated from a healthy swarm if that single IP experiences downtime or throttling.

Conclusion

While it might seem beneficial to seed a torrent from the same IP or machine multiple times, it can actually be detrimental in terms of tracker efficiency, swarm health, and detection of unfair practices. It's better to have a diverse set of peers contributing to the swarm, both in terms of IP addresses and geographical location, to ensure a robust, high-performing, and fair torrent environment.

Action you must take Now!

Stop seeding the same torrent twice from the same IP address and location.

Further Action

Should you not comply with our request, your account will be disabled.

Thank you for your co-operation.

-[BT-BOT]