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

[I2P] [Feature Request] Support i2p_pex extension #7269

Open
zzzi2p opened this issue Jan 16, 2023 · 8 comments
Open

[I2P] [Feature Request] Support i2p_pex extension #7269

zzzi2p opened this issue Jan 16, 2023 · 8 comments

Comments

@zzzi2p
Copy link

zzzi2p commented Jan 16, 2023

ref: https://geti2p.net/en/docs/applications/bittorrent

@stale
Copy link

stale bot commented May 21, 2023

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.

@stale stale bot added the stale label May 21, 2023
@stale stale bot closed this as completed Aug 13, 2023
@anikey-from-i2p
Copy link

anikey-from-i2p commented Jan 27, 2024

So, is this implemented or not? (Asking because it says "closed this as completed")
If not then it's kinda weird that this bot can just come around and close issues like on a whim.

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.
So ok, if it's closed because stale, then i probably should subscribe to this issue to then leave comments like "it's still a problem".

@mpeter50
Copy link

mpeter50 commented Jul 8, 2024

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).

@Neustradamus
Copy link

@arvidn: Can you reopen this ticket?

@mpeter50
Copy link

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.

@arvidn
Copy link
Owner

arvidn commented Jan 27, 2025

first draft: #7831

@Neustradamus
Copy link

@zzzi2p: The @arvidn PR has been merged:

It is good for PEX now?

I2P BitTorrent details:

What is missing to have a perfect BitTorrent and I2P support now?

@arvidn: Can you check DHT?

Thanks in advance.

@zzzi2p
Copy link
Author

zzzi2p commented Jan 31, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants