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

Document DHTCommunity #1087

Closed
qstokkink opened this issue Apr 11, 2022 · 1 comment · Fixed by #1330
Closed

Document DHTCommunity #1087

qstokkink opened this issue Apr 11, 2022 · 1 comment · Fixed by #1330
Assignees
Labels
documentation ReadTheDocs or docstrings priority: low Should be addressed at some point in the future

Comments

@qstokkink
Copy link
Collaborator

The DHTCommunity (and its subclass the DHTDiscoveryCommunity) have very useful functionality to store data and to connect to peers based on their public key. This functionality allows IPv8 to serve as both a distributed file system and allows programmers to both create neighborhood persistence and superpeer networks.

We may want to leave IPv8-as-a-file-system functionality out of the documentation to avoid competing with Tribler's solution. However, it would be useful to give an example of storing known peers on custom Community.unload() and attempting to reconnect when initializing (i.e., neighborhood persistence). This one example would also cover "find-your-friend"/superpeer functionality.

@qstokkink qstokkink added priority: low Should be addressed at some point in the future documentation ReadTheDocs or docstrings labels Apr 11, 2022
@qstokkink
Copy link
Collaborator Author

This tutorial could build off of the Network snapshotting used in the TriblerTunnelCommunity (see https://github.com/Tribler/tribler/blob/76ed927339a73d7b3c8464e8a4b43cf8a520e2d2/src/tribler/core/components/tunnel/community/tunnel_community.py#L134-L161).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation ReadTheDocs or docstrings priority: low Should be addressed at some point in the future
Development

Successfully merging a pull request may close this issue.

1 participant