Alex Potsides

Closing due to staleness

Closing because the v2 implementation will be all that's supported in the future so traffic forwarding for remote hosts via the relay will not be supported.

The final piece here is for interested modules to tag peers they need to keep connections open to. - [x] @libp2p/bootstrap https://github.com/libp2p/js-libp2p-bootstrap/pull/142 - [x] @libp2p/kad-dht https://github.com/libp2p/js-libp2p-kad-dht/pull/375 - [x] @chainsafe/libp2p-gossipsub https://github.com/ChainSafe/js-libp2p-gossipsub/issues/380

Closing as this is now complete. > maxConnections should not mean "disconnect a random peer if above this limit", but instead mean "prevent new connections from being created if at...

Having spent more time that I'd like to admit pushing changes around during the IPFS Althing I am becoming more amenable to this as I'd like to spend more time...

Another problem that we have is releasing changes to modules ahead of libp2p. For example the next libp2p release changes the peer store to be atomic, so that means: 1....

1. 👍 🙏 2. All supported modules have been moved in. Archiving and issue triaging on the older repos is still in progress. With the exception of the consolidated interface...

Since https://github.com/libp2p/js-libp2p/pull/1498 when passed a multiaddr, only that multiaddr is dialed so this is no longer possible. There's a possible edge case where if you dial a peer id, then...

Closing due to staleness - please reopen if this is still breaking things

Sounds great. Would PRs that move this module closer to the spec be accepted?