Treat same files as ONE torrent with sub-torrents to respect each private site individuality. #15986

New issue

Open

opened 2026-02-22 02:41:10 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:41:10 -05:00

Owner

Originally created by @ghost on GitHub (Aug 14, 2024).

Suggestion

Treat same files as ONE torrent with sub-torrents to respect each private site individuality.

On user-side show a single torrent to respect User energy - minimise user effort and automate everything as much as possible.

When the same torrent is seeded on multiple trackers - treat the thing as ONE unit presented to the client, but with a GUI page where its clearly visible each separate torrent for each tracker where its seeded.

Including and especially if the files are with different names, some files are added, some files are missing, some are in archive, treat it all as ONE unit.

Let download from fastest source even if unsure of hash - verify hashes after completion. Especially useful when one tracker has no seeders for torrents with renamed files.

Example specific case: NFO file unix and windows formats, I think on TL its windows format and on IPT etc is Unix format (original). (Actually this is an edge case.)

Use case

Very often same content is reshared multiple sites.

Extra info/examples/attachments

No response

Originally created by @ghost on GitHub (Aug 14, 2024). ### Suggestion Treat same files as ONE torrent with sub-torrents to respect each private site individuality. On user-side show a single torrent to respect User energy - minimise user effort and automate everything as much as possible. When the same torrent is seeded on multiple trackers - treat the thing as ONE unit presented to the client, but with a GUI page where its clearly visible each separate torrent for each tracker where its seeded. Including and especially if the files are with different names, some files are added, some files are missing, some are in archive, treat it all as ONE unit. Let download from fastest source even if unsure of hash - verify hashes after completion. Especially useful when one tracker has no seeders for torrents with renamed files. Example specific case: NFO file unix and windows formats, I think on TL its windows format and on IPT etc is Unix format (original). (Actually this is an edge case.) ### Use case Very often same content is reshared multiple sites. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

label

2026-02-22 02:41:10 -05:00

deekerman commented

2026-02-22 02:41:17 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

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:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
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.)

@xavier2k6 commented on GitHub (May 25, 2025): ## 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.)**