Thomas Eizinger

I am reopening this because: - the orthogonality of the static keep alive mechanism with the remaining ping functionality is highlighted once again in https://github.com/libp2p/rust-libp2p/pull/2852 - I find `DummyBehaviour` to...

We have experimented with libp2p and Tor a lot and landed on the following: 1. It is quite easy to do a dial-only transport: https://github.com/comit-network/xmr-btc-swap/blob/master/swap/src/network/tor_transport.rs 2. In our experience, Tor...

> Perhaps relevant [blog.torproject.org/arti_100_released](https://blog.torproject.org/arti_100_released) the Tor project released Arti v1, their new Rust based Tor implementation. That is big news indeed. Reading through the blogpost under the "What's coming next?"...

> I started working on this, however I have issues dealing with Multiaddress correctly. As far as I can tell Multiaddress comes with some support for Onion out of the...

I would suggest we make use of the `cargo-xtask` pattern: https://github.com/matklad/cargo-xtask/

I've played around with Google's `release-please` and it works quite well. Here is an example of a release PR: https://github.com/thomaseizinger/rust-libp2p/pull/5 - It builds on the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/). This should...

> I took a look at [cargo-release](https://github.com/crate-ci/cargo-release/). As far as I can tell from a small dry-run cargo-release could simplify the last step of a release, namely the publishing of...

> For the record, I did the `v0.49.0` release with `cargo release`. #3028 updates our release documentation accordingly. > > This tool makes my life A LOT easier. Wonderful. That...

I think the document we have is up to date with our release process. I do think we should change it though. All the manual steps like changelog entries and...

> I assume this is known, but I didn't see it mentioned here: js-libp2p is using release-please I believe. I did not know this! Thanks for mentioning it. @achingbrain @MarcoPolo...