trust

This is to help people that for whatever reason don't want to go through the effort of changing it manually every time.

Default levels of understanding and thoroughness for both positive (review)and negative(flag) could also be configurable in the user-config file.

Currently we use the word "Option" which is inconsistent and may cause confusion.

Example:

# Option: "alloc" enables support for heap allocation on "no_std"
# platforms, requires nightly.
alloc = ["ockam_core/alloc", ...

Should rather be:

# Feature: "alloc" enables support for heap allocation on "no_std"
# platforms, requires nightly.
alloc = ["ockam_core/all

vcn n git://... is actually notarizing just the commit which HEAD is pointing to.

If there're untracked files or changes not staged, then both notarization and authentication will ignore them.

A simple solution would be to show a warning message when the working tree is not clean, so the user will be aware that pending modifications are not part of the notarization/authentication process.

Steps to reproduce:

1. Open demo app
2. Scan QR code to identify yourself
3. Switch demo to "simple encryption"
4. Encrypt something
5. Decrypt it

The Cogito mobile app now shows a Touch ID / Face ID message because the private key is needed. There is no explanation provided as to why, however: the Touch ID / Face ID dialog should have explanatory text.

While looking at this, it is prob