Compatibility with cross-seed

[luckylittle]

I think there needs to be a way to differentiate unique and non-unique torrents as well as option to disable DeleteData only for non-unique.

For example - at the moment, tqm clean qbt --dry-run with this config:

filters:
  default:
  DeleteData: true
    ignore:
      - IsTrackerDown()
      - Downloaded == false && !IsUnregistered()
    remove:
      - IsUnregistered()

Produces output where it targets both unique/non-unique:

...
removing unregistered non-unique torrent (file overlap): "<TITLE>"
removing: "<TITLE>"
...

I imagine there must be a common scenario, where people want to remove unregistered torrents in such a way, that:

• if the torrent is unique (not cross-seeded), i want to remove it including all of the data => complete wipe
• if the torrent is non-unique (cross-seeded), i just want to remove it from the client, but keep the data intact as other trackers might be using it

[saltydk]

We already do that.

…

On Tue, Jul 22, 2025, 04:51 Lucian Maly ***@***.***> wrote: *luckylittle* created an issue (autobrr/tqm#73) <#73> I think there needs to be a way to differentiate unique and non-unique torrents as well as option to disable DeleteData only for non-unique. For example - at the moment, tqm clean qbt --dry-run with this config: filters: default: DeleteData: true ignore: - IsTrackerDown() - Downloaded == false && !IsUnregistered() remove: - IsUnregistered() Produces output where it targets both unique/non-unique: ... removing unregistered non-unique torrent (file overlap): "<TITLE>" removing: "<TITLE>" ... I imagine there must be a common scenario, where people want to remove unregistered torrents in such a way, that: - if the torrent is unique (*not* cross-seeded), i want to remove it including all of the data => complete wipe - if the torrent is non-unique (cross-seeded), i just want to remove it from the client, but keep the data intact as other trackers might be using it — Reply to this email directly, view it on GitHub <#73>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSIMLRJ5PT6IYM74PAJIHD3JWRJ5AVCNFSM6AAAAACCBO2AF6VHI2DSMVQWIX3LMV43ASLTON2WKOZTGI2TANZYGY4DINQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[luckylittle]

Perhaps, it is just the dry-run that needs to have better output?

[saltydk]

Dry run is indeed not very useful for this edge case currently.

[luckylittle]

As per our Discord discussion, I found an "issue" specific to relabeling the TMM torrents which share the same data (cross-seeded). This is typically used to move old torrents to a different location/hard drive after a certain time:

• qBt Torrent Management Mode: Automatic
• qBt When torrent category changed: Relocate torrent

When you want everything SeedingDays >= 7.0 relabeled, run tqm relabel qbt -v --experimental-relabel against these torrents:

1. rhel-10.0-x86_64-boot.iso 3d 8h (seeded for 3d 8h) 816 MB /home/user/LINUX_ISOS
2. rhel-10.0-x86_64-boot.iso 8d 2h (seeded for 8d 2h) 816 MB /home/user/LINUX_ISOS
3. rhel-10.0-x86_64-boot.iso 8d 2h (seeded for 8d 2h) 816 MB /home/user/LINUX_ISOS
4. rhel-10.0-x86_64-boot.iso 8d 3h (seeded for 8d 3h) 816 MB /home/user/LINUX_ISOS
5. rhel-10.0-x86_64-boot.iso 8d 3h (seeded for 8d 3h) 816 MB /home/user/LINUX_ISOS

However, it only relabels 2.-5. and ignores the 1. because it does not meet the condition. So there are two things that I was expecting - either:

• it would not relabel at all, because one of the torrents does not match the condition >=7
• it would relabel all of them as they share the underlying data, because at least on matched the condition >=7