-
Notifications
You must be signed in to change notification settings - Fork 1.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
Project Flare / Hole Punching tracking issue #1122
Comments
Moving to #1039. |
I'm reopening this because #1039 has been closed but we have more to do here before "Project Flare" is "done". I believe having no open project flare issues causes confusion. People think it's done, when there is more to do. What does "done" mean?
@marten-seemann : happy to discuss this more here or in #libp2p-dev. I know my list above is likely incorrect. I assume you'll update the issue description to describe what actually remains. Thanks! |
I disagree.
That's #1351.
That could be a testground issue, but doesn't justify keeping this issue open in my opinion. We have a lot of stuff we want to test better, and it makes little sense to keep the original "implement the feature" issue open for all of them. Looks like we already have issues for those. Why is that not good enough?
That should be an issue in go-ipfs, not in go-libp2p.
This issue here was created erroneously, that's why it was closed the same day. If at all, #1039 should have been reopened, not this one. |
@marten-seemann : I'm game to work in any issue. It sounds like #1039 is preferred. I want to have a way to be clear that "hole punching in go-libp2p is done to a state that we recommend key consumers like go-ipfs and lotus enable it by default". #1039 was closed before we hit that state, so I assumed it was denoting a different milestone. I'll plan on commenting more in #1039. |
Circuit v2
Tentative timeline: Get this ready for the go-ipfs v0.10 release.
Hole Punching
Tentative timeline: We should defer enabling this until a critical mass of nodes have upgraded and are running v2 relays.
AutoRelay
Once a critical mass of v2 relays has been deployed, rewrite the code to use v2 relays (reserve slots and refresh reservations).
The selection logic should be two-fold:
The text was updated successfully, but these errors were encountered: