Remove duplicate trackers without announce

[Misiek304]

trafficstars

I have a small list of trackers that are added automatically to the torrents:

udp://9.rarbg.me:2710/announce
udp://9.rarbg.to:2710/announce
udp://exodus.desync.com:6969/announce
udp://glotorrents.pw:6969/announce
udp://open.demonii.com:1337/announce
udp://tracker.coppersurfer.tk:6969/announce
udp://tracker.internetwarriors.net:1337/announce
udp://tracker.leechers-paradise.org:6969/announce
udp://tracker.openbittorrent.com:80/announce
udp://tracker.opentrackr.org:1337/announce
udp://tracker.sktorrent.net:6969/announce
udp://tracker.x4w.co:6969/announce
udp://zer0day.ch:1337/announce

They all have the /announce at the end of the address. Now with some torrents qBittorrent is adding additional trackers with the same addresses but without /announce which makes a mess and forces additional connections to the tracker. For example:

udp://9.rarbg.me:2710/announce
udp://9.rarbg.me:2710
udp://9.rarbg.to:2710/announce
udp://9.rarbg.to:2710
udp://exodus.desync.com:6969/announce
udp://exodus.desync.com:6969
udp://glotorrents.pw:6969/announce
udp://glotorrents.pw:6969
udp://open.demonii.com:1337/announce
udp://open.demonii.com:1337

Could there be maybe a function to ignore trackers with /announce or any other additional information after the proper address and port? Here is a bit different issue but affected by the same problem: https://qbforums.shiki.hu/index.php?topic=1783.0

[Theli93]

FWIW: Because of its nature/function, use of "/announce" for UDP protocol is redundant and effectively useless.

This does not apply to HTTP and HTTPS trackers, where it reamains a necessary part of the address.

[FranciscoPombal]

some torrents

I tried with several torrents on the latest stable PPA version (4.1.9.99~201911020617-6737-5d98721~ubuntu18.04.1) and I cannot reproduce. Perhaps this has already been fixed in the meantime?

If someone can reproduce this, please specify the torrent's name (or maybe just its infohash...), otherwise this can be closed.

[badjuice]

Is this on the roadmap?

[xavier2k6]

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future! Here are some options available to you:

1. Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.

2. Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket. (new/existing contributors/developers are always welcome)

---

DO:

• Provide constructive feedback.
• Display how other projects implemented same/similar etc.

DO NOT:

• Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). (These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)