No, DHT is just a way of determining paths and priority of value lookup by key in the network, so that the load were distributed predictably, while allowing you to find, well, what you are looking for. BTW, while everybody uses Kademlia with modifications, I’d argue that Chord is better for anything related to security and anonymity.
Storage and serving of anything big is another thing. I take it you mean that I2P nodes cache messages relayed via them when the target node is unavailable. That doesn’t have anything to do with DHT.
I2P has its own internal DHT network. Bote piggybacks on it to relay messages between Bote nodes. You can even configure it so you can address random online nodes and ask them to hold a message for another node to relay (online or offline) to obscure message timing
DHT can be used for almost anything as a generic key value store, even if the typical use is just peer finding
OK, I really love I2P, just wish sometimes there would be ways to use it with latency and throughput approaching clearnet. I like that it’s a platform solving the P2P and discovery problems for everyone in the same way and providing interfaces for that, but the privacy and security orientation means that it’s mostly used for privacy and security (even pedo filesharing doesn’t seem to be too many people).
Can’t really do that with volunteer nodes only in open networks. Reliable low latency anonymous connections require stable direct links between most nodes. Like you’d need a bunch of big universities to run it.
It does temporarily, on the order of hours to days. It’s not designed to use the network for long term storage, just message passing
No, DHT is just a way of determining paths and priority of value lookup by key in the network, so that the load were distributed predictably, while allowing you to find, well, what you are looking for. BTW, while everybody uses Kademlia with modifications, I’d argue that Chord is better for anything related to security and anonymity.
Storage and serving of anything big is another thing. I take it you mean that I2P nodes cache messages relayed via them when the target node is unavailable. That doesn’t have anything to do with DHT.
I2P has its own internal DHT network. Bote piggybacks on it to relay messages between Bote nodes. You can even configure it so you can address random online nodes and ask them to hold a message for another node to relay (online or offline) to obscure message timing
DHT can be used for almost anything as a generic key value store, even if the typical use is just peer finding
https://bote.readthedocs.io/en/latest/v5/kademlia/
Ye-es, but wouldn’t that be kinda slow?
Correct, and slow is kinda the point (traffic metadata protection through timing obfuscation)
There’s even a setting to set multiple Bote hops (inside I2P which already use multiple hop tunnels) with random delay per node (up to 24h)
OK, I really love I2P, just wish sometimes there would be ways to use it with latency and throughput approaching clearnet. I like that it’s a platform solving the P2P and discovery problems for everyone in the same way and providing interfaces for that, but the privacy and security orientation means that it’s mostly used for privacy and security (even pedo filesharing doesn’t seem to be too many people).
Can’t really do that with volunteer nodes only in open networks. Reliable low latency anonymous connections require stable direct links between most nodes. Like you’d need a bunch of big universities to run it.