Fix add data operation not working correctly

Reminder: do not get reference to hash map value... duh

Add thread-safe logging (log is in order now!).
Store data immediately to database when WE add it instead of waiting for
response from remote peers.
TODO: Test with multiple peers (not only localhost)

1 files changed, 6 insertions, 0 deletions

diff --git a/README.md b/README.md
index d5035d5..7a81580 100644
--- a/README.md
+++ b/README.md
@@ -9,9 +9,15 @@ Only 65kb of data can be used for each `add`. You can add more data by using `ad
 User and group name can't be longer than 255 characters.
 
 # TODO
+## Data limit
+Allow more than 65kb of data to be added at once
 ## Node banning
 Ban nodes that spam put or get (malicious nodes). If data is routed, then the router node should first ban the malicious node so the router node is not banned if it's not malicious.
 But how can we know if data was routed? does opendht expose this to other nodes in some way?
+
+Another method could be for nodes to be required to generate a key pair that takes long time to generate and sign messages with them.
+If we are spammed with the same key pair, we can ban messages that comes from that key pair. The malicious node would require to generate a new key pair
+which would take some time (we can make key generation take 60 seconds).
 ## Error handling
 Currently operations are executed without knowing if they succeed or not. Operations should be modified to perhaps return std::future or use a callback function which is called with the operation result.
 ## Safely store private keys