oskarth

Related https://github.com/vacp2p/rfc/issues/494

Great stuff! What do you think of Waku mode (with mailserver support) as a possible "trojan horse" to get Nim into the app as an option?

@arnetheduck Ack and agree. FWIW, the current spec for kad-dht is currently in WIP PR for 1y+ (https://github.com/libp2p/specs/pull/108), and there's a protobuf in rust-libp2p here: https://github.com/libp2p/rust-libp2p/blob/master/protocols/kad/src/dht.proto - I did base...

The latest is that we want to figure out a better discovery interface for the parts that modify libp2p directly (switch, etc), then split Kademlia up into a separate repo....

Nevermind, it seems like it works as expected. I thought the identify exchange failed, but seems like it was a separate issue. The node can connect with TCP regardless of...

Currently, I believe all of these types of modules would interact with nim-waku, above nim-libp2p. E.g. RLN spam protection is wrapping a Rust library with Nim bindings and being imported...

^ @adambabik @mandrigin @PombeirP @dshulyak

The point is there should be some way for endpoint to limit traffic, for example a la how BT client does it. IIRC mailserver uses TCP. If packets are dropped...

Sounds good, I think we need to figure out better semantics for mailserver re bursts. > keep receiver buffer full That's what I was referring to - you are right,...

It was during Hackathon and intermittent, @adambabik @PombeirP @jakubgs has more. The point of original issue IMO is more to make sure it can never happen again.