Create Multi-Torrent...

[MjngoCTV]

Is there a possible working way, sams fashion as per backup torrents for leeching/downloading, to create a seeding torrent that connects to multiple trackers simultaneously?

At the moment, have to create separate seeding torrents for each tracker, even though content is exactly same.

Thanks in advance.

[Firon]

If the torrents have the same infohash, then you just add the tracker URL for all those trackers to it with a newline between each one, either when creating it, or after loading it in the torrent properties.

[phaelox]

will that not screw up tracker ratios, by say reporting to tracker1 amounts downloaded/uploaded to/from peers received from tracker2, and vice versa?

[Firon]

It'll report the same amounts to every tracker, which is probably a good thing for you.

[splintax]

Unless the tracker admins detect that and ban him.

[Firon]

It's not very likely to happen.

[nightshifted]

If the torrents have the same infohash, then you just add the tracker URL for all those trackers to it with a newline between each one, either when creating it, or after loading it in the torrent properties.

My experience with that is that µTorrent just keeps announcing only to one of them, and the way I read the multi-tracker spec, I'm not so sure that's wrong (though it certainly is not what I want). Even removing the original URL and leaving only the new one doesn't always seem to make it announce to the new URL.

A way to make µTorrent announce to more than one tracker at the usual half-hour intervals, or at least to make it announce to another tracker once (like BitTornado's manual announce feature), would be nice, but I'm not going to scream for them.

[Firon]

Not if they're in different groups (shown by having an empty newline between the trackers), it will announce to all of them at the same time. And it still cycles the tracker in the same group on each announce.

[phaelox]

It'll report the same amounts to every tracker, which is probably a good thing for you.

OK, I think I'll avoid doing that on private trackers then.

[nightshifted]

Firon: that's what I expected, but it's not what I'm getting. (My fault for not specifying in #34630 that I was leaving the blank line between them.)

[Firon]

Not here, I see it cycle constantly, and it always updates both tracker groups.

[nightshifted]

Using two groups of one tracker each, if I set the screen refresh to 1000 ms, the displayed tracker alternates each refresh; if I set it to 2000 ms, it cycles maybe every third or fourth.

Anyhow, the problem seems to be that I'm testing it under wrong circumstances, trying to use two (valid) passkeys on one tracker rather than two trackers. The tracker won't let the same peer ID change user accounts in mid-stream. If I stop and start, returning with a new peer ID, it may pick up either username, depending on which passkey is in the first announce.

If I were on a torrent on two trackers, then things would work out properly. The multi-torrent spec was not intended for the situation where I'm testing it (in those days, a tracker had only one announce URL); that just happened to be the most convenient testing ground for me.

Surely if there were actual different trackers in my test, the results would be the same as Firon's.

[Firon]

Well, they were the same tracker in my case, just with different ports. But I guess it counts as two separate trackers.

[nightshifted]

It depends on what the tracker does with them. My guess is that µTorrent was announcing to both but that as long as the passkey was valid, the peer_id overrode it.

[MjngoCTV]

Thanks everyone for your input and explanations, appreciated.

The question, how to make torrent(s) to have the same infohash, so that can just add the tracker URL for all thee trackers to it, with newline between each one as usual, since each tracker needs submission and generates its own torrent link?

[chaosblade]

If you create the torrent with multipile trackers defined, and upload it at some tracker, it should not change the trackers inside. I've seen some scripts modify the private flag or so, but it should not erase your extra\different trackers.

[Firon]

Adding a tracker URL does not modify the infohash in any way. If the torrent is made properly, the infohash shouldn't differ on any of the sites. But you never know.