There are some cases I am not able to cross seed.
I'm talking about private trackers and identical torrents.
So I already have downloaded a torrent from tracker A and want to cross seed it to tracker B.
When I open the .torrent file in qbittorrent, I get the message "Torrent Name is already in the transfer list. Trackers cannot be merged because it is a private tracker".
Option to merge trackers to existing torrent in advanced settings is unchecked.
Why doesn't it create a new independent torrent which will contain only the new tracker?
Is there any way to solve this and cross seed?

Originally Posted by ganja7

There are some cases I am not able to cross seed.
I'm talking about private trackers and identical torrents.
So I already have downloaded a torrent from tracker A and want to cross seed it to tracker B.
When I open the .torrent file in qbittorrent, I get the message "Torrent Name is already in the transfer list. Trackers cannot be merged because it is a private tracker".
Option to merge trackers to existing torrent in advanced settings is unchecked.
Why doesn't it create a new independent torrent which will contain only the new tracker?
Is there any way to solve this and cross seed?

The client just looks at the hash value it doesn't care what the name is or what trackers you're reporting to.
You could try using a different client?
I thunk there's software that helps do it in the same client but I've never used it so I can't help

Originally Posted by Squidgy

The client just looks at the hash value it doesn't care what the name is or what trackers you're reporting to.
You could try using a different client?
I thunk there's software that helps do it in the same client but I've never used it so I can't help

Shouldn't it open the add torrent dialog box so I could check "Skip hash check"?
If I want to use another client for cross seeding, I assume that I have to move every torrent that is currently cross seeding in qbt, to that client. Correct?
I ask that because there are some torrents cross seeding at the moment in qbt that didn't have any problem to be added.
Do you mean this?
https://github.com/cross-seed/cross-seed

Originally Posted by ganja7

Shouldn't it open the add torrent dialog box so I could check "Skip hash check"?

My understanding is that that is just "rechecking" the files - as in checking to make sure the file has the expected hash value - it still needs to check the hash value in the torrent because it needs to announce it to the tracker

Originally Posted by ganja7

If I want to use another client for cross seeding, I assume that I have to move every torrent that is currently cross seeding in qbt, to that client. Correct?

I just meant if you have 2 clients running and only 1 of the torrents in each you shouldn't have any issues with the client trying to merge them. So if you have torrents that are cross seeding fine you can leave them, and any problem torrents to the second client.

Originally Posted by ganja7

I ask that because there are some torrents cross seeding at the moment in qbt that didn't have any problem to be added.

If its the exact file but the torrent is made with different piece sizes it will register separately, If the original uploader wanted to cross seed they probably would have done this. Also there's a "source tag" when creating torrents that can force it to a particular tracker to help with cross seeding.

Originally Posted by ganja7

Do you mean this?
https://github.com/cross-seed/cross-seed

Yeah seems about right

Originally Posted by Squidgy

I just meant if you have 2 clients running and only 1 of the torrents in each you shouldn't have any issues with the client trying to merge them. So if you have torrents that are cross seeding fine you can leave them, and any problem torrents to the second client.

I meant that there are some torrents within qbt that are already cross seeding at the moment but some will not(the initial issue I have). As far as I know I can't seed torrents from the same tracker in different clients, can I?

Originally Posted by ganja7

I meant that there are some torrents within qbt that are already cross seeding at the moment but some will not(the initial issue I have). As far as I know I can't seed torrents from the same tracker in different clients, can I?

I've never seen any rules about it, a lot of the time you can't seed from 2 IPs at the same time but I think different clients on the same IP is okay. Check with the tracker before hand

Originally Posted by Squidgy

The client just looks at the hash value it doesn't care what the name is or what trackers you're reporting to.
You could try using a different client?
I thunk there's software that helps do it in the same client but I've never used it so I can't help

I think you more close to reality
I tried to upload something to bitspyder, I am shocked with my client which can`t do something
after a while I tried to troubleshoot it, I found out only specific utorrent version used to upload

Really??????
I've been doing this a long time now...
It's either no problem or... I didn't get caught yet!

Well, you know how I got the idea? (wasn't mine really...)
There were some uploaders who were uploading on multiple trackers, and if you'd check the tracker list you'd see all the different trackers there.
How do they get away with it if it's not permissible?

Edit: Although I see your point! Definitely the stats won't be correct...never thought of that!

Originally Posted by loukoumas

Really??????
I've been doing this a long time now...
It's either no problem or... I didn't get caught yet!

Well, you know how I got the idea? (wasn't mine really...)
There were some uploaders who were uploading on multiple trackers, and if you'd check the tracker list you'd see all the different trackers there.
How do they get away with it if it's not permissible?

Edit: Although I see your point! Definitely the stats won't be correct...never thought of that!

If it was public trackers its okay. In most tracker rules theres something about it.
Here's REDs rule -embedding non-Redacted announce URLs in Redacted .torrents is prohibited. Doing so causes false data to be reported and will be interpreted as cheating. This applies to standalone .torrent files and .torrent files that have been loaded into a client.

Your client basically reports the upload to the trackers, if you have 2 announce URLS you're uploading to both but reporting the same amount to both. So you might upload 2gb - 1gb to RED and 1gb to OPS, but you would report 2gb to both.
Smaller trackers might not be monitoring to see if people are incorrectly reporting, but its definitely possible to check and the decent trackers will be able to tell

Originally Posted by Squidgy

If it was public trackers its okay. In most tracker rules theres something about it.
Here's REDs rule -embedding non-Redacted announce URLs in Redacted .torrents is prohibited. Doing so causes false data to be reported and will be interpreted as cheating. This applies to standalone .torrent files and .torrent files that have been loaded into a client.

Your client basically reports the upload to the trackers, if you have 2 announce URLS you're uploading to both but reporting the same amount to both. So you might upload 2gb - 1gb to RED and 1gb to OPS, but you would report 2gb to both.
Smaller trackers might not be monitoring to see if people are incorrectly reporting, but its definitely possible to check and the decent trackers will be able to tell

No, it's not public trackers and yes, they are small trackers, maybe that's why I didn't have any problems.
All in all, I'm only cross-seeding a few torrents.
When I first started, I put them on 2 separate clients (and left them there)
Then I discovered the "merging" possibility and did that with the next couple torrents.
Never thought I could be cheating, that was not my intention...
So now, I'll put those two "offending" torrents on different clients and that will be it!
Thanks for bringing this to my attention!