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

Bittorent multi-trackers tiers #86

Open
poeml opened this issue Jun 5, 2015 · 0 comments
Open

Bittorent multi-trackers tiers #86

poeml opened this issue Jun 5, 2015 · 0 comments
Labels

Comments

@poeml
Copy link
Owner

poeml commented Jun 5, 2015

                                                                                  [          ]

Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue86

Title    Bittorent multi-trackers tiers
 Priority   bug    Status   in-progress
Superseder        Nosy List Kelson, nemobis, poeml
Assigned To poeml Keywords  torrents

msg329 (view) Author: Kelson Date: 2011-03-10.12:51:51

Mirrorbain seems to always put the trackers, in case of multitrackers, in one
and unique tier.

See doc:
http://www.scribd.com/doc/13839289/BitTorrent-MultiTracker-Specification

This has for consequence, if you want to rely on multiple tiers (better
robustness), that if you have only one seeder, this one could be unreachable by
a potential leecher. The reason is the suffle introduced in the tier by the client.

For this reason, it seems to me to be important to be able to configure many
tiers to be able to force the bittorrent clients to try trackers in a specific
and predifined order.

msg330 (view) Author: poeml Date: 2011-03-10.20:30:45

Hm, let me see if I understand correctly.
MirrorBrain 2.15.0 does the following:

% curl -s 'http://download.services.openoffice.org/files/stable/3.3.0/OOo-
SDK_3.3.0_Solaris_Sparc_install_en-US.tar.gz.torrent' | bdecode | grep announce
{'announce': 'http://bt.mirrorbrain.org:8091/announce',
'announce-list': [['http://bt.mirrorbrain.org:8091/announce',
'udp://bt.mirrorbrain.org:8091/announce']],

Are you proposing to use the form

[ [tracker1], [backup1], [backup2] ]

instead of

[[ tracker1, tracker2, tracker3 ]]

?

Is that generally better, or should it be configurable?

msg331 (view) Author: Kelson Date: 2011-03-11.08:34:12

I think you understand well what I mean.

I know this multitracker feature only since yesterday.

I dicovered it by investigating why time to time clients are not able to join my
superseeder, and mainly use the webseed.

So I'm not a bittorrent expert and although It seems to me that the first
alternative should be what people mainly need, I won't say this should always
work like that.

I think we have also to take care to not change the meaning of the
"MirrorBrainTorrentTrackerURL" directive.

So, IMO this should be configurable.

You could maybe add a new Apache directive. Something like
"MirrorBrainNewTorrentTrackerTier" which would allow to split groups of
trackers/MirrorBrainTorrentTrackerURL directives

msg416 (view) Author: nemobis Date: 2013-02-20.08:58:24

To clarify, from a UI perspective, uTorrent, Transmission and so on show
different trackers with their backup URLs like this:

udp://tracker.publicbt.com:80/announce
http://tracker.publicbt.com:80/announce

udp://tracker.openbittorrent.com:80
http://tracker.openbittorrent.com/announce

Newline between different URLs for same tracker, double newline for new tracker.
MirrorBrain puts all trackers together, so they are treated as a single tracker.
This is an actual bug, not a feature request.

msg417 (view) Author: poeml Date: 2013-02-24.09:39:24

Thanks, I should look at it...

History
         Date          User   Action              Args
2013-02-24 09:39:25 poeml   set    status: chatting -> in-progress
                                     messages: + msg417
                                     priority: wish -> bug
2013-02-20 08:58:24 nemobis set    nosy: + nemobis
                                     messages: + msg416
2011-03-11 08:34:13 Kelson  set    messages: + msg331
                                     assignedto: poeml
2011-03-10 20:30:46 poeml   set    messages: + msg330
                                     keyword: + torrents
                                     nosy: + poeml
2011-03-10 12:51:51 Kelson  create

(end of migrated issue)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant