raulk

@stebalien @vyzo we probably want to start moving on this soon.

Calling out @vyzo @bigs specifically for a first round of review. A bunch of things are now depending on the dialler changes (self-dial, prioritising non-relay addresses, etc.), so we should...

@bigs has stepped up to move this PR over the finish line :-)

Resuming this thread. @vyzo: > I would like to have a mechanism to supply at a minimum the address resolver for individual dial jobs. IMO, that would be too complex....

If this becomes a common case, we introduce an higher-level `AddressResolverDispatcher` that conforms to the `AddressResolver` interface and proxies a bunch of address resolvers behind a set of predicates. The...

This fails CI because of https://github.com/libp2p/go-libp2p/issues/736.

## Next steps - reporting: `cluster:k8s` and `local:docker` should monitor the state of the sidecars and print a warning to OutputWriter when any of the sidecar fails. -- right now...

On the sending side, gossipsub coalesces pubsub messages (on the same or different topics) that are directed to the same peer within one aggregate protobuf wire message (which also contains...

@protolambda wanted this too

@yusefnapora let's tag-team on this, if you have cycles.