Hey Christian, First of all thank you for the answer.
Actually, I'm thinking of creating a `social blog` application in which friends connect to friends. I was hoping for some way of ensuring persistence of content across a (social) network. The friend peers could best be providing for the storage of the content, doing away with the need of random unrelated peers providing the storage. The thing is, I'm expecting the content to be small text messages a lot of the time. I think the filesharing subsystem might be a little bit to much overhead for this, considering that file blocks are 1024 bytes, and there is a lot of functionality that I don't need for this. Any ideas? Otherwise, I will probably have to create my own subsystem for this I guess. I was just looking at DHT and hoping it would fit my use case. If I had the ability to have the friend peers store the content without the need of the originator of the content to be online, I would have been there. Thanks. Danny On Wed, 2021-02-17 at 12:29 +0100, Christian Grothoff wrote: > Nope, datastore is _only_ for the file-sharing subsystem, datacache > is > for the DHT (alas DATACACHE does not have such an API, you must use > the > GNUNET_DHT_put-API). > > Happy hacking! > > Christian > > On 2/17/21 11:57 AM, Danny wrote: > > Hey guys, > > > > Quick question. > > Can I use GNUNET_DATASTORE_put for manually storing content that > > would > > be available by DHT GET requests from others nodes? > > > > Thanks! > > Danny > > > > > > >
