-
Notifications
You must be signed in to change notification settings - Fork 451
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
Dispersy: peer discovery community (no more initial bootstrap servers) #13
Comments
Attempt to fix most of the unittests + removing old legacy code.
As commented we also need this to do a "No-Internet-Needed" smartphone app |
For the No-Internet-Needed stuff we need to be able to discover peers without having to rely on any tracker. |
Some history, in March 2006 we already worked on this stuff: http://web.archive.org/web/20060429043719/http://tribler.org/developers/?layer0=105 |
Discovery community and peercache.txt files are implemented/integrated |
@synctext but we aren't bundling one with Tribler yet, so the bootstrap servers are still needed. |
To bootstrap the search, allchannels and other communities we currently require connectable servers.
The aim of this enhancement is that all connectable peers automatically form a community bootstrap overlay. An alternative is to use our DHT, but connectability and lack of NAT-awareness make this less attractive. Similar to the Kazaa 2001 and Buddycast 2005 design we probably better use a local host-cache with the 200+ peers which we've seen in every community.
The Tribler installer will no longer include a hard-coded list of 16 bootstrap servers, but a "peer_cache.txt" with a few hundred peers to find the network. On a daily basis we refresh this peer_cache with stable connectable peers. Plus we put this updated file in the Linux/Mac/Windows installers.
The text was updated successfully, but these errors were encountered: