Ignore duplicates missing

[KyleSanderson]

Now that the index is searchable (nice!) - hopefully the ignore duplicates flag from autodl-irssi becomes a thing as there are much better ways to handle this now.

[ludviglundgren]

I converted this to a GH Discussion for now. We have talked a lot about this in Discord in the past but information and discussions easily gets lost.

Lets start to define what a duplicate is since it can be many things.

Examples:

• Full release name
• Show/game/title
• Combo of title, resolution, group etc
• Same release on multiple indexers
• Season and episode

Should it be static or configurable? A basic solution would be faster to develop but might not be what users are looking for.

All feedback are welcome 😃

[KyleSanderson]

Ultimately, what constitutes a dupe is if the same content is there. So improving upon what autodl-irssi had would be if the content layout is the same as the existing file (or, converted to match the same layout, either modifying new or existing depending on what's possible). If there are additional files on the new submission (Sample/Srt as an example) that should still count as a duplicate. Parsing the title for Title / Season / Year / Episode should be considered hints, but as some folks retag the exact same content it's not required. Piece size should be ignored.

[KyleSanderson]

Specifically from qBittorrent this is exposed through the files API as far as I'm aware.

[LSL1337]

I think short term solution could be that if the izem has the same name, it should be considered as duplicate.
Maybe it can be added with regardless of resolution.
If i download episode1 1080p, other episode 1 releases can be ignored.
More logic would make it much harder to implememt, and it would still be short of sonarr/radarr. But this could cover a lot of use cases, which are not compatible with sonarr/radarr. (Sports for example)

[luckylittle]

It has been a while since this discussion started - can we do something really simple to start with? This is a number one feature that I am really missing. Simple to me is: if the release name exactly matches and the push on the first one was successfully approved, then ignore all of the sub-sequential pushes. I don't need to wait for it to complete - some 0day trackers can push the same release within a few seconds from each other.

Pseudo code was mentioned previously here: #375 (comment)

[KyleSanderson]

Upgraderr has existed for years, and is documented on autobrr.com