Joseph Werle
Joseph Werle
@telamon nope! EDIT: if ` const other = hypercore(ram, publicKey, { valueEncoding })` dropped the `valueEncoding`, it will still replicate, but the contents of the data storage are encrypted
"after verification" means that just after hypercore has verified the checksum of the merkle tree, it calls a "write hook" as seen [here](https://github.com/mafintosh/hypercore/blob/master/index.js#L916), [here](https://github.com/mafintosh/hypercore/blob/master/index.js#L941), and [here](https://github.com/mafintosh/hypercore/blob/master/index.js#L994) It is a powerful...
@telamon yep. One could also just a regular hypercore for the writer and when swarming the write hook encrypts data sent to peers so readers are working with an encrypted...
@yuridiniz yeah go for it! I think I'd like to come back to this sometime in the near future and make this API enforce the caller to allocate memory. This...
yeah.. this needs to be refactored [this](https://github.com/littlstar/b64.c/blob/master/encode.c#L41) is bad this would probably solve it: ``` c tmp = (char *) realloc(enc, size + 4); if (NULL != tmp) { enc...
hmm...! did you fix all `realloc() calls ?
@stephenmathieson yeah absolutely
Related to #16
@d21d3q looks good!