emilbayes
commented
4 years ago Yeah so it's legacy is TweetNaCl which you can still find the original copyright for:
However we wanted to have a more modular browser version of libsodium, rather than emscripten version like libsodium.js, and then along the way wasm became an option. I think that's pretty much it?
The "ecosystem" here is:
- sodium-native is "ground truth"
- sodium-tests is testing parity between sodium-javascript and sodium-native
- sodium-universal is the automatic switch between either in whatever environment you use the module in
Some newer goals are to conform to sodium-native returns, which TweetNaCl did not, make it modular so you can import the pieces you need, try to avoid Buffers to keep the browser bundle smaller, and have sensible assertions in the same manner as sodium-native
Hope that clears up a bit
christianbundy
Hi. After spending a few hours working on this project I've found myself feeling curious about the history.
My best guess is that this is meant to be like TweetNaCl-JS except with a libsodium API, but I figure I should probably just ask rather than make assumptions. Thanks for the fun project!