Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better handling of duplicated torrents/magnets #234

Open
drws opened this issue Jul 16, 2023 · 2 comments
Open

Better handling of duplicated torrents/magnets #234

drws opened this issue Jul 16, 2023 · 2 comments

Comments

@drws
Copy link

drws commented Jul 16, 2023

Currently when a torrent/magnet with the same hash as one of the existing ones is added, nothing happens. The user should be informed in such case and ideally even offered to merge useful info from it. For example if a magnet link with only a hash is added and another one with the same hash but also containing a file/folder name is added later on, the missing information could be extracted and used. The same goes for the tracker list. It would be a great feature to be able to quickly merge additional trackers from a later-found torrent or a magnet link instead of throwing the valuable information away.

@LaserEyess
Copy link
Member

FWIW, I also think the daemon should help out by detecting and doing something about dupes. But all of the information is present in TRG so we could do something, too.

@drws
Copy link
Author

drws commented Jul 17, 2023

The proposal upstream exists for some time already. Also it appears that Transmission rejects a duplicate with a message, but it seems that it doesn't get through the remote GUI (where nothing happens).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants