Alexis Sellier 4c1aa65f90 node: correct handling of announcement timestamps ...

Since we now have three announcement message types, we need at least
three timestamps per peer. But even that is not enough, since we don't
want to conflate ref announcements for different projects with each
other.

The solution is to also keep a map of timestamps per peer, for each
tracked project. That way we are able to know when a ref announcement is
interesting to us or not.

Signed-off-by: Alexis Sellier <alexis@radicle.xyz>

2022-10-14 11:59:54 +02:00

.github/workflows

Update Rust to 1.64

2022-09-26 11:27:31 +02:00

.nix

meta: add nix tooling

2022-10-12 12:21:01 +02:00

radicle

node: Handle node announcements

2022-10-14 11:58:17 +02:00

radicle-node

node: correct handling of announcement timestamps

2022-10-14 11:59:54 +02:00

radicle-ssh

ssh: remove unused traits, simplify code

2022-10-13 22:33:36 +02:00

radicle-tools

radicle: namespace peers

2022-10-12 12:30:05 +02:00

.gitignore

Initial commit

2022-09-13 10:13:13 +02:00

Cargo.lock

Statically link sqlite3

2022-10-12 13:27:45 +02:00

Cargo.toml

Add SSH functionality with new radicle-ssh

2022-10-03 10:34:59 +02:00

rust-toolchain

Update Rust to 1.64

2022-09-26 11:27:31 +02:00

S

Description

Radicle Heartwood Protocol & Stack

40 MiB

Languages

Rust 97.8%

Shell 0.5%

CUE 0.4%

Nix 0.3%

Just 0.3%

Other 0.6%