- `wrap_api_future` function did not exist, so I used `wrap_api_future_plain` since the return type appears to be a base64 encoded string.
- Argument order for `create_dht_record` was incorrectly swapped.
- `veilid_core::json_as_base64` does not exist, don't exactly know what to replace it with for serde serialization, but I commented it out for now.
- Removed `--no-typescript` flag from `wasm-buildgen` so that TypeScript types are emitted.
Added the standard Python entries to gitignore plus included
veilid-python/demo/.demokeys to prevent personal keys from
being saved in the upstream repository
Both sides of the chat now generate secrets based on their private key
and the other side's public key. They encrypt each message with a nonce
before sending it, and use the nonce in the decryption.
This _does_ mean that the responder has to specify the starter's name
now so that they can select the proper public key for encryption.
This cleans up some types, moves some typing to loading and saving keys,
uses clearer object names, and passes a crypto system into chatter.
This lays the groundwork for adding encryption.
Python chat demo
A Python based demonstration app which facilitates a 1:1 conversation between two parties. Routing privacy is enabled in this initial version.
See merge request veilid/veilid!106
Added and modified documentation for the contribution process.
Added the code of conduct file.
Modified bump version's conf to auto create tags and commits.
The original thinking was that if len(b) < FIXED_SIZE, then that would
be picked up later by the "invalid member length" check. In that case,
this only really *needs* to make sure that the check after this for
"wrong fourcc" wouldn't fail. But if len(b) < FIXED_SIZE, it really is
an invalid size, and should get that error message before even starting
to validate its other qualities.
