inih VS libhydrogen

This looks interesting. I created and maintain a library for INI parsing that got surprisingly popular -- it's tiny, so is good for embedded systems. This API has a very similar feel to mine, including the callback for every key/value pair with a void* userdata. https://github.com/benhoyt/inih

I don't know if it's the best place to post that but on the meson subreddit there is not much people. I want to include the library INIH (which use meson too) to my project but I don't know how.

One simple format is INI, which has the benefit of being simple and ubiquitous. It has rules for quoting and whitespace. It's human readable and human editable. ini.h is a very simple INI parser library, but there are loads of them.

The single round-trip initial Diffie-Hellman key exchange is susceptible to MITM attack, as has been demonstrated to me by a fan of the project. I'll be changing it to XX key exchange from libhydrogen. Either directly, or I'll use libsodium primitives to reimplement the same thing.

See if you can use this library instead of libsodium, as it'll probably work on your raspi zero: https://github.com/jedisct1/libhydrogen (Node bindings: https://github.com/trampi/node-libhydrogen-binding)

Are you possibly thinking of libhydrogen?

https://github.com/jedisct1/libhydrogen

NIST's lightweight cryptography contest is still in progress. When it finishes I'd definitely change to whatever wins. In the iterim you might want to look into the candidates. I happen to like gimli, see libhydrogen for a good library that uses it.