Prithvi Shahi

It requires @marten-seemann 's review afaik it's not blocked on the performance work.

Sorry, I only assumed it was a blocker for merging the PR but not subsequent re-reviews. Chinmay says he was blocked on re-review [here](https://filecoinproject.slack.com/archives/C03RAB14HCG/p1673023560127749) and [here](https://filecoinproject.slack.com/archives/C03RAB14HCG/p1671832080697779). There may have been...

That sounds like a good idea, there should be an accompanying blog post as well.

Closing this as it's addressed by https://github.com/libp2p/specs/pull/453 and implemented by https://github.com/libp2p/go-libp2p/pull/1813

For now this has been deprioritized in favor of go-libp2p WebRTC work per https://github.com/libp2p/go-libp2p/pull/1655#issuecomment-1319368953

Being tracked here: https://github.com/libp2p/js-libp2p/issues/1608

closing in favor of https://github.com/libp2p/js-libp2p/issues/1461 AutoNat has landed https://github.com/libp2p/js-libp2p/issues/1005 hole punching in the browser is possible via private-to-private/browser-to-browser https://github.com/libp2p/js-libp2p-webrtc

The subject of migrating js-libp2p components into a monorepo was brought up by @MarcoPolo and discussed in the 2023-03-07 js-libp2p triage meeting with @achingbrain @wemeetagain @maschad and @p-shahi The reasons...

Merging interfaces into internal/interfaces and external/interfaces would be a breaking change. Maintainers have decided to wait on this for a bit, since 0.45.0 was a big breaking change release as...

non-interface modules to monorepo added in https://github.com/libp2p/js-libp2p/pull/1828