-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[I2P] [Feature Request] Support i2p_pex extension #7269
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
So, is this implemented or not? (Asking because it says "closed this as completed") I'm not saying that it must be done quickly (because i already appreciate and respect all the work that has already been done), but this is something that would be useful, and the most important thing for this is to not close this on a whim. |
This most probably wasnt implemented, just the faulty bot closed it as completed. The issue should be reopened and a label added that stops it from autoclosing it, and the bot should be fixed to close stale issues with the "not planned" status (though this latter thing probably does not depend on arvidn). |
@arvidn: Can you reopen this ticket? |
If you read this, I think it would be worth to consider reopening it, as the comments and some reactions to them this year indicate interest in the feature. |
first draft: #7831 |
Not up to me to declare it good or offer advice on perfection. I assume you all are testing and looking for i2p_pex messages in and out, to snark and bigly. If somebody wants me to get on a torrent and do some snark logging to verify, find me on irc2p #i2p-dev. DHT is 10x or 100x harder, you can't make it happen by bugging people. |
ref: https://geti2p.net/en/docs/applications/bittorrent
The text was updated successfully, but these errors were encountered: