Thomas Eizinger

Would it make sense to integrate this directly into `cargo check` and run it by default? The "no-false-positive" mindset seems like this would be safe! Alternatively, it could also be...

We now have the ability to implement arbitrary connection management so I think the other usecases for configurable mDNS name is resolved.

> @thomaseizinger I have recently stumbled into this issue writing a new application using `rust-libp2p`. I've written an mDNS application that was unnecessarily attempting to communicate with a local kubo...

> > If a [private network](https://github.com/libp2p/specs/blob/master/pnet/Private-Networks-PSK-V1.md?rgh-link-date=2024-06-16T15%3A47%3A21Z) is in use, then the service-name contains the base-16 encoding of the network's fingerprint as in _p2p-X._udp.local. This prevents public and private networks from...

Another update on this: I've introduced a builder pattern to builder the initial handler. This makes it much more convenient to configure a handler that doesn't accept inbound streams for...

The latest patches introduce the notion of a `Stream` handler which allows us to implement protocols such as `libp2p-ping` that reuse their stream and emit events as they go along....

Rendezvous is now also fully migrated and functional.

I think this is ready for a proper review @mxinden @jxs @elenaf9! I've updated the PR description.

I think we can close this as won't-merge. It was an interesting exploration though!

> Still interested to get this merged @thomaseizinger! Writing a tiny protocol right now where this would come in handy for testing. Ah yes, me too. I'd prefer if we...