Max Inden

Closing here due to staleness.

`Error: UnknownProtocolId(465)` should be from rust-multiaddr: https://github.com/multiformats/rust-multiaddr/blob/master/src/errors.rs#L15 More specifically it is the `webtransport` protocol: https://github.com/multiformats/multiaddr/blob/master/protocols.csv#L28 The Rust client doesn't support `webtransport` in the first place, thus fine to ignore the...

Still facing the issue. Haven't done any further debugging. Glad I seem to be the only one.

The optimization is meant for the honey pot, not for the hole punching clients. Keeping the connections to the (potentially behind a firewall) remote peer alive, as the honey pot,...

Low priority: - By default go-libp2p aims to listen via [2 relay nodes](https://github.com/libp2p/go-libp2p/blob/031ec50a04507cb2def993ef0ad15cf95eb98922/p2p/host/autorelay/options.go#L43). I wonder whether these values are good as is, too high or too low. Questions could be:...

In the case of TCP and QUIC, we could disable one locally and thus test the other.

One advantage I would like to add: - `prost` conveniently generates Rust code into `target/` without the code having to be checked into git. In general I have had only...

We could do something similar to https://github.com/spacejam/sled/pull/1076 falling back to a `Mutex` on platforms without `AtomicU64` along the lines of what https://github.com/bltavares/atomic-shim does. What do you think @n4ss @breeswish?

I am not sure I understand the issue at hand correctly. As far as I can tell both `AtomicU64` and `AtomicI64` are not supported on 32-bit PowerPC. Thereby this is...

Thanks for the detailed suggestion @tim-seoss. > I think offering AtomicU32 (or AtomicUsize) is probably the best thing to do on platforms which don't have 64 bit integer atomic types....