{"action":"created","issue":{"url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/2928","labels_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/2928/labels{/name}","comments_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/2928/comments","events_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/2928/events","html_url":"https://github.com/qbittorrent/qBittorrent/issues/2928","id":72403958,"number":2928,"title":"Allow duplicate torrents","user":{"login":"build-system","id":7596905,"avatar_url":"https://avatars.githubusercontent.com/u/7596905?v=3","gravatar_id":"","url":"https://api.github.com/users/build-system","html_url":"https://github.com/build-system","followers_url":"https://api.github.com/users/build-system/followers","following_url":"https://api.github.com/users/build-system/following{/other_user}","gists_url":"https://api.github.com/users/build-system/gists{/gist_id}","starred_url":"https://api.github.com/users/build-system/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/build-system/subscriptions","organizations_url":"https://api.github.com/users/build-system/orgs","repos_url":"https://api.github.com/users/build-system/repos","events_url":"https://api.github.com/users/build-system/events{/privacy}","received_events_url":"https://api.github.com/users/build-system/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-01T10:35:42Z","updated_at":"2015-05-01T17:49:06Z","closed_at":null,"body":"[Since version 2.2.0][changelog], qBittorrent checks whether the torrent you're adding is already on the list. If it is, then it automatically merges the trackers of both torrents under a single torrent. While this is a useful feature, there are situations where it is undesirable.\r\n\r\n[Many trackers keep download and upload statistics for every user][private-torrents]. Torrents downloaded from these trackers come with only one tracker URL and often have the private flag set. The same content may be available on multiple trackers and the user can seed on all of them — a practice known as cross-seeding. However, when all trackers are using the exact same torrent file, qBittorrent will merge the trackers under a single torrent.\r\n\r\nThis is undesirable because the client will report upload and download statistics incorrectly. If you upload some gigabytes to a peer from one tracker, this will be announced to _all_ trackers. From the tracker's point of view, the user is cheating ratio by pretending to upload data that wasn't actually uploaded and therefore in grave violation of the rules. This feature can thus result in the loss of an ill-advised user's account. People who are aware of this problem recommend the use of another client in order to work around the issue. It would be nice if they didn't have to resort to that.\r\n\r\nA good way to avoid this problem is to simply ask the users whether they want to merge the torrents instead of making that decision for them. Another solution: don't merge torrents with the private flag set. Even an option buried deep under the `Advanced` section would be nice.\r\n\r\n [changelog]: https://github.com/qbittorrent/qBittorrent/blob/8c671fa0c1efa72eef4c12a0dffe7de4cbbc6ad4/Changelog#L287\r\n [private-torrents]: http://www.bittorrent.org/beps/bep_0027.html"},"comment":{"url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/comments/98186429","html_url":"https://github.com/qbittorrent/qBittorrent/issues/2928#issuecomment-98186429","issue_url":"https://api.github.com/repos/qbittorrent/qBittorrent/issues/2928","id":98186429,"user":{"login":"sledgehammer999","id":273315,"avatar_url":"https://avatars.githubusercontent.com/u/273315?v=3","gravatar_id":"","url":"https://api.github.com/users/sledgehammer999","html_url":"https://github.com/sledgehammer999","followers_url":"https://api.github.com/users/sledgehammer999/followers","following_url":"https://api.github.com/users/sledgehammer999/following{/other_user}","gists_url":"https://api.github.com/users/sledgehammer999/gists{/gist_id}","starred_url":"https://api.github.com/users/sledgehammer999/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sledgehammer999/subscriptions","organizations_url":"https://api.github.com/users/sledgehammer999/orgs","repos_url":"https://api.github.com/users/sledgehammer999/repos","events_url":"https://api.github.com/users/sledgehammer999/events{/privacy}","received_events_url":"https://api.github.com/users/sledgehammer999/received_events","type":"User","site_admin":false},"created_at":"2015-05-01T17:49:06Z","updated_at":"2015-05-01T17:49:06Z","body":"**The only viable option here is to not merge torrent for private trackers(and display an explicit message for that).**\r\nThe infohash is used by qbt to identify the different torrents in the session. And I am not even sure if libtorrent supports the having the same torrent in the session, 2 times with different trackers.\r\nYou might be interested to make a suggestion in libtorrent-rasterbar's bugtracker, to have an option to somehow post different stats on each tracker for private torrents. (Based on from where it got it's peers) Or something like that.\r\nPS: I am editing your title and message to reflect my decision."}}