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
..
address	node: Handle node announcements	2022-10-14 11:58:17 +02:00
client	Implement routing table persistence	2022-10-05 12:13:12 +02:00
service	Improve error handling in a few places	2022-10-10 11:29:22 +02:00
test	node: Handle node announcements	2022-10-14 11:58:17 +02:00
wire	node: Handle node announcements	2022-10-14 11:58:17 +02:00
address.rs	node: Handle node announcements	2022-10-14 11:58:17 +02:00
client.rs	node: Handle node announcements	2022-10-14 11:58:17 +02:00
clock.rs	Refactor service	2022-09-23 15:43:55 +02:00
control.rs	Implement routing table persistence	2022-10-05 12:13:12 +02:00
decoder.rs	node: Rename folder to `radicle-node`	2022-09-21 11:38:09 +02:00
lib.rs	node: Handle node announcements	2022-10-14 11:58:17 +02:00
logger.rs	node: Rename folder to `radicle-node`	2022-09-21 11:38:09 +02:00
main.rs	Add `Profile::connect`	2022-09-26 14:27:56 +02:00
service.rs	node: correct handling of announcement timestamps	2022-10-14 11:59:54 +02:00
test.rs	Rebroadcast logic for stored gossip messages	2022-09-29 10:02:52 +02:00
transport.rs	node: Handle node announcements	2022-10-14 11:58:17 +02:00
wire.rs	node: Handle node announcements	2022-10-14 11:58:17 +02:00