Jacob Heun

> The best approach is defaulting to not announcing local network addresses unless explicitly added as announce addresses. With this approach, how would you announce your local network addresses? Right...

Also, @vasco-santos have you looked at the way go-libp2p composes the announced addresses? It would be helpful to document that here so we can clarify any differences.

For dialing I think implementing the ConnectionGater, https://github.com/libp2p/go-libp2p/issues/872, is going to be the best approach here, we can create a default Gater similar to https://github.com/libp2p/go-libp2p/pull/1005. We'll need to figure out...

Accidentally closed this, this request looks good to me. I think adding inbound only hangups via options would be nice to have as well.

The core update will need to happen in switch (so maybe it shouldn't have been an easy label, lol). Luckily the recent updates I did for better connection tracking should...

It's possible for us to have more than one incoming/outgoing connection per peer, although it will currently try to minimize that. Thinking through this a bit more I don't think...

Yes, to the logic flow. I think adding that could be helpful. Along with the peerInfo we can send a metadata object so that we can more easily add additional...

That code should only run during an outgoing connection. When an incoming connection occurs it's added here https://github.com/libp2p/js-libp2p-switch/blob/v0.41.3/src/connection/manager.js#L183. The incoming connection creates the FSMConnection already muxed, so the upgrading logic...

I think the simplest solution here is to indeed just expose the raw connection. Right now that's hidden in the `Connection` interface, but if we expose the underlying `MultiaddrConnection` you...

We are planning on picking this back up this quarter, it's just lower on the priority list at the moment. The next steps for moving this forward are to finalize...