The same question was archived on r/trackers. Would like to get notified when a compatible tracker is available for testing, it’s not even clear if there is an implementation just yet.

The specs are here since 2017 https://www.bittorrent.org/beps/bep_0052.html
Compatible clients are available, at least qBittorrent (from v4.4.0) and BiglyBT.

  • bear_with_a_hammer@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    1 year ago

    No, not yet, this question was probably posted by me. I’m one of the provocators to switch to the new protocol.

    The thing is the most tracker admins are:

    1. Too lazy to implement it.
    2. Have too little information about its benefits.
    3. Only heard downfalls associated by compatibility problems, which were exxagerated by people who don’t like to update their software.

    I even created a tool called tmrr. Which allows you to extract, compare and calculate file hashes (BTMR hash precisely — BitTorrent Merkle Root, hence it differs from a regular sha256) name for BitTorrent v2 compatible .torrents.

    Which already shows some advantages of use of the protocol in user environment, like finding same torrents contents with different names, reviving dead torrents, preserving historical Internet artifacts’ hashes.

    The final feature I’m going to release is the ability to download torrents without duplicates (first time in the history of BitTorrent), saving time, storage and bandwidth. Imagine downloading site, page dumps, libraries, video/photo archives and other uncategorized materials without duplicate files.

    Easily finding how much user storage specific game and its developers wasted due to ineffective coding.

    This feature is ready, but there are some problems in libtorrent (library that qBittorrent uses), which should be fixed by the next release (this year probably) to make it work.

    Hope this will get attention from users and accelerate the switch.