Jacob Heun

> Hi! Is this on the table for Q2? It would be really nice to have for ipfs-deploy. Yes. This is on my list for the quarter and I am...

@suutaku what does your network setup look like in terms of libp2p nodes? Are you connecting both nodes to the same signaling server? The chat example at https://github.com/libp2p/js-libp2p-examples/tree/master/chat provides a...

@suutaku are they both connected to a signaling server? You'll need to add listening addresses to both nodes for the signaling server, until we get a decentralized signaling protocol in...

@suutaku hole punching definitely is not 100%. WebRTC has our only method of doing this in JS right now. There are other NAT traversal techniques we're working on adding, but...

The other really nice thing we could do with this not listed is releasing preconfigured libp2p nodes more easily with every libp2p release so users don't have to configure anything...

cc @achingbrain @hugomrdias @vasco-santos

> @jacobheun we should default PeerId.create to use ed25519 keys as well. When would be a good time for that in this timeline? @vasco-santos we could time a breaking change...

The major outstanding issue left for this is Keychain support for ed25519 keys, which is due to a lack of [import/export support](https://github.com/libp2p/js-libp2p-crypto/issues/145) in js-libp2p-crypto.

>1. the peer:connectis received by the emitting node, several times. i.e the node seems to connect to itself Incoming dials may log multiple connections. The reason for this is that...

@vasco-santos @dirkmc I've written down some thoughts around this. It also made me think more about how service configuration works currently and how it can improve, but I've left that...