Alex Potsides

I've tried to add a global count to the WebTransport transport to ensure we don't go over 64 "pending" connections, taking "pending" as meaning "has yet to resolve/reject the `.ready`/`.closed`...

A [comment](https://bugs.chromium.org/p/chromium/issues/detail?id=1473980#c11) on the Chromium bug links to [this design doc](https://docs.google.com/document/d/1u2kcv3YjvxMc91xylGAyhP1UhxAr2ZobgvCaL37AOUM/edit) - it seems Chromium unilaterally applies an anti-DOS measure by keeping "failed" connections in the "pending" state for 5...

Ref: https://github.com/ipfs/in-web-browsers/issues/211#issuecomment-1953218400

Notes from Igalia work stream (under various `Handling pending WebTransport sessions` headers): https://hackmd.io/SaJIHZmyRUKfl_fQwoYfog

Is there a way we can do this in stages to prevent it causing libp2p v2? Perhaps just adding the private key in the first instance, then releasing it, then...

Superseded by #2660

@akim-bow what kind of addresses are you having problems with? The example you gave was `[/dns/nox-1, /ip4/10.50.10.10, /ip4/127.0.0.1]` - DNS addresses take time to resolve, so that can be bad,...

My concern with the proposed solution is that having separate timeouts for individual addresses could lead to very long dial times. I wonder if we could be smarter with the...

Depends on: - [x] https://github.com/ChainSafe/js-libp2p-noise/pull/440

Could these options be consolidated? It would avoid the situation where a user sets both `runOnSelfUpdate` and `disableIdentifyPush` to `true` and expects something to happen. Also, can you add some...