Max Inden

Results 900 comments of Max Inden

Posting some in-progress research on the various Rust QUIC implementations out there. ### Verdict Thus far my preference is still `quinn` via https://github.com/libp2p/rust-libp2p/pull/3454. - We know at least `quinn-proto` works...

**Status Update** https://github.com/libp2p/rust-libp2p/pull/3454 merged and thus our `libp2p-quic` implementation depends on upstream `quinn` directly. Thank you @kpp for the work. In case no major blockers are discovered in `libp2p-quic` `v0.9.0-alpha`...

**Status Update** We just released [`libp2p` `v0.52.3`](https://github.com/libp2p/rust-libp2p/releases/tag/libp2p-v0.52.3) which contains a stable release of `libp2p-quic` `v0.9.2`. That is the first stable `libp2p-quic` release in rust-libp2p and thus a big step for...

I am closing here as the major milestone, adding QUIC to rust-libp2p, is achieved. Smaller follow-up improvements are tracked in individual issues. Thank you to the many many many people...

I am still in favor of this change. @efarg let me know in case you are still interested in contributing this change. (Sorry in case I am missing a related...

> 1. f somehow possible, I'd like to get rid of `IntoConnetionHandler` and delay calling `new_handler` until we have established the connection. This would allows us to directly make `new_handler`...

We do still need a mechanism for a `NetworkBehaviour` to allow or deny pending inbound or outbound connections. (In https://github.com/libp2p/rust-libp2p/pull/2828 that happens via new methods on `NetworkBehaviour`.)

> The second failure point can be used for established connections and policies like banning by peer ID. But that second failure point needs some synchronization mechanism back to a...

We had multiple requests for rust-libp2p to be able to prevent dialing any private IP addresses. Thus far we have pointed them to the following `Transport` wrapper: https://github.com/mxinden/kademlia-exporter/blob/master/src/exporter/client/global_only.rs Somehow I...

Agreed with the concerns above. I suggest continuing with the custom `Transport` implementation for now.