Group the "same tracker" with different protocol into tiers

[flueflacks]

in the all list, group http/https/udp/ws etc to the same host, into the same tracker tier. (ie in one set of lines with no newline between them)

this will prevent redundant requests to what is likely the same tracker.

see https://github.com/flueflacks/gettrackers which does this on the command line.

[ngosang]

Which bittorrent clients support trackers list with "tiers"?

[flueflacks]

my understanding is Bep-12 "Multitracker Metadata Extension" is supported by most modern torrent clients.

qbitorrent definitely supports both tiers the empty line separated lines as a way of separating the tiers.

I assumed because your tracker lists are in empty line separated format that most clients do the same. but i haven't confirmed.

[ngosang]

I assumed because your tracker lists are in empty line separated format that most clients do the same. but i haven't confirmed.

As far as I’m aware, there is no formal standard for plaintext tracker lists. The BEP 12 discusses “lists of lists” as a way to represent tiers within the .torrent metadata, but it doesn’t define any format for sharing tracker lists externally. My impression is that when the BitTorrent protocol was designed, the assumption was that the trackers included in the .torrent file would be fairly static and wouldn’t need frequent updating.

I currently use the format that uTorrent has supported for about 20 years, but since it’s closed source, I don’t know exactly how it parses those lists.

Do you have any additional information on this topic?

Could you share links to the parts of the source code where popular BitTorrent clients parse tracker lists?

[flueflacks]

but it doesn’t define any format for sharing tracker lists externally

agreed.

Do you have any additional information on this topic?

I don't. we'll see if i can find anything.

but i concur, it may not be worth doing if there's no standard for importing/sharing them.