Marten Seemann

@Kubuxu Nothing new here. I just moved the issue to go-libp2p because we've moved go-libp2p-quic-transport into go-libp2p. No idea why GitHub is sending out notifications for that :(

Huh, how did this issue get closed? Looks like it happened when I merged go-libp2p-quic-transport into this repo (https://github.com/libp2p/go-libp2p/pull/1424), and GitHub applied the comment referring to the fix of https://github.com/libp2p/go-libp2p-quic-transport/issues/238...

This has now been released in [quic-go v0.22.0](https://github.com/lucas-clemente/quic-go/releases/tag/v0.22.0), so we can flip the switch any time we want.

Open question: Is there any way to find out Prometheus' scrape frequency, so we can adjust our collection interval?

> What else can we do? We cant let the other side ping ad infinum and squat the resources. True. There are multiple options: 1. We could limit the client...

> lets punt on this for now go-libp2p v0.17.0 is out now. I'd really like to get this into v0.18.0. Not having duplicated code for our hosts is a prerequisite...

Right, the blankhost used by autonat today doesn't have identify.

> @mxinden @marten-seemann @aschmahmann when are we enabling RelayClient and hole punching? go-ipfs 0.12? We still don't have quite enough relays on the network yet, but we're getting close. Given...

@Y-A-K-E Why would that be? If so, that would be a bug. Can you share some more details?

> Overall I'm open to this. Maybe later, once HTTP/3 is finalized and has broad client support. @mholt HTTP/3 is (basically) finalized. The QUIC transport documents have completed IETF Last...