-
Notifications
You must be signed in to change notification settings - Fork 291
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
DHT addon #93
DHT addon #93
Conversation
Reviewed 2 of 2 files at r1. Comments from Reviewable |
Can you make the callback stateless as described in #40? Also, the merge commit is empty, you can remove it. |
Do we want this in toxcore master? |
I don't think we do |
This allows developers to leverage the DHT without using a third party implementation or having to write their own (which is very helpful for certain use cases). On the other hand, it's not used by the core itself and is not required for typical client usage, so it could be considered unnecessary. Is low-level access to the DHT something we want toxcore supply? If so, this probably belongs in the public API. Right now it's written as a bit of a hack and doesn't really fit in anywhere. |
I feel that creating a low level DHT access to the network can be helpful for some clients that want finer control over statistics or who you set as bootstrap nodes. Developers having an easier time means better apps get developed and more user growth. |
I'm all for adding this as an undocumented, unsupported API. I'm not sure if this is the BEST way to go about it. But isn't not the worst way. |
My thoughts on this: #119 |
Please discuss this change with irungentoo on the PR you made on his repo. If you have thoughts on #119, please post them there. You're very welcome to contribute ideas for a generalised DHT API that this callback could be part of. |
allows for 3rd party apps to harvest DHT info
This change is NOT reviewable. Use Github reviews instead.