Max Inden

I would welcome this change. @dignifiedquire do you want to propose a patch?

I can't comment on the Golang specifics. Referencing the corresponding specification issue here: https://github.com/libp2p/specs/issues/21 See also [Future work](https://github.com/libp2p/specs/blob/master/relay/README.md#future-work) section in relay specification.

> Having it in another repo makes it a bit harder (I have PTSD from outdated examples & tutorials :D ) Agreed. I think example code should live as close...

For the reasons outlined by @Menduist in https://github.com/libp2p/docs/issues/245#issuecomment-1337610963 I don't think we should move the Rust examples here, unless we can enforce in an automated way that they will never...

:wave: (rust-)libp2p maintainer here. > does the noise transport support sending authenticated data along with the initial handshake? The Noise framework does. libp2p does not (yet). See https://github.com/libp2p/specs/issues/498 for embedding...

I don't have access to a punchable NAT right now. Do you @thomaseizinger? If so, mind running this version of the Rust punchr to test https://github.com/libp2p/rust-libp2p/pull/3454?

Results from a cafe: 

Good question. As far as I know not visible through the Grafana dashboard. Ran locally once more. The 4 last successful hole punches were all `/quic-v1`.

I suggest we merge here only after https://github.com/libp2p/rust-libp2p/pull/3454.

Still facing trouble with the Nix build. I don't foresee us using the Rust punchr client much in the future, especially not by external folks. Thus I am not going...