Thomas Eizinger
Thomas Eizinger
Let me know if this is still an issue.
> I see, actually, I just wanted to advocate for getting rid of libsodium. It increases build time on dev builds by a lot. On that matter, see https://github.com/libp2p/rust-libp2p/pull/3212#issuecomment-1345555434.
I think we can close this. The dalek crates are now maintained again and not far off a release.
> Worth a new issue, @thomaseizinger? Yeah I'd say so. Might be worth discussing over at https://github.com/libp2p/specs. > Also, can I take a moment to ask what paperwork I have...
Happy to first have a discussion in this repo and exchange some ideas. Posting in specs often has quite the blast radius so it might be better to hash out...
Planning this for the next milestone.
We now have https://github.com/umgefahren/libp2p-tor.
> @thomaseizinger was there any technical reason that you remember why you didn't mention `libp2p-tokio-socks5` in this thread but instead referenced the xmr-btc-swap code (although the code looks pretty similar...
This is stale and has been resolved by trimming down `ListenUpgradeError` to just the error emitted by `InboundUpgrade`.
**Changelog:** Added link to https://github.com/kpp/rust-libp2p/pull/27#discussion_r1018147667 so we don't forget to refactor the TLS-config handling.