Torrents should contain a nodes key #49

Closed
poeml opened this Issue Jun 5, 2015 · 0 comments

1 participant

@poeml
Owner
                                                                                  [          ]

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

Title    Torrents should contain a nodes key
 Priority   wish        Status     resolved
Superseder            Nosy List    poeml
Assigned To poeml      Keywords

msg172 (view) Author: poeml Date: 2010-03-31.19:46:27

Torrents should contain a nodes key.

Harold: uTorrent uses the nodes key for backup DHT bootstrapping information
incase other "more primary" information fails

It sould be made configurable with different servers.

There is documentation at http://www.bittorrent.org/beps/bep_0005.html that
suggests that nodes keys should be added only for trackerless torrents, but Harold
said that information is outdated since the core change (BitTorrent.com switched
to the uTorrent core).

Note: remove source code comment in mod_mirrorbrain.c about this.

msg194 (view) Author: poeml Date: 2010-05-29.12:07:17

Fixed in trunk (r8068).

http://svn.mirrorbrain.org/viewvc/mirrorbrain?view=revision&revision=8068

I used http://opensource.depthstrike.com/torrent.php/MPlayer-
1.0rc2.tar.bz2.torrent as (hopefully valid) example.

To configure the nodes, a MirrorBrainDHTNode config directive was added, which
takes two arguments (hostname and port).

History
         Date         User  Action              Args
2010-05-29 12:07:18 poeml set    status: in-progress -> resolved
                                   messages: + msg194
                                   priority: feature -> wish
                                   status: unread -> in-progress
2010-03-31 19:46:27 poeml set    messages: + msg172
                                   nosy: + poeml
                                   assignedto: poeml
2010-03-31 19:44:12 poeml create

(end of migrated issue)
@poeml poeml closed this Jun 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment