Kim Altintop

That makes sense, if the `org-node` port is unique per `radicle.eth` CNAME (assuming that's the p2p port). That is, `x.radicle.eth` has a different port than `y.radicle.eth`, and the client has...

Ah, sorry: our CI is currently tagging the image only by commit SHA1 (not "latest" or anything). Try: docker pull gcr.io/opensourcecoin/radicle-seed-node:f1462b92a06ef65ec4b65201e9801473a41b4ee3

The image simply sets the `radicle-seed-node` binary as the entrypoint. So whatever CLI arguments you'd pass to `radicle-seed-node`, you'd pass to `docker run`. Try `docker run gcr.io/opensourcecoin/radicle-seed-node@sha256:714b84d6d3d872620291a6ffd34bf14555750dd6cabd9a76fa77c2b389624a03 --help`

This would potentially be possible if `radicle-link` programs persist their partial view of the network upon (graceful) exit. I don't think there's a way to react to `PING` frames in...

I think a good start would be to use `cargo` versioning and tag the releases -- we should also come up with a versioning scheme where it's clear when there's...

Due to the wonderful ways of async Rust. See radicle-dev/radicle-link#505

It is actually somewhat hilarious how inefficient this is in theory. Either I'm missing something, or life was a little easier on MySQL.

It has been concluded that for the use-case of radicle-dev/radicle-upstream#965, a simple one-way attestation in the other direction suffices, and can be expressed with a much more compact proof: Consider...

What I’m saying is that `tracing` is somewhat, err, non-obvious to hold right, but is designed with all the service-mesh-grade ‘ilities in mind. For example, there is a way to...

https://github.com/ipfs-rust/quinn-noise/issues/2