crates

In the docs, there are several cases such as here where code snippet examples are shown side by side, without actually specifying which files they are (eg. deny.toml vs Cargo.toml) which can lead to confusion for users. Every code snippet should just specify # <name>.toml at the top for clarity.

This is a tracking issue for additional Store implementations.

Here is a non-exhaustive list of potential candidates for an Store implementation:

• S3Storage:
  This would store crate tarballs and rendered README pages into Amazon's S3.
• RemoteStorage:
  Requires to implement a companion server.
  The idea is to have a reserved folder on another machine which runs a comp

Currently, cv-pinhole has the essential matrix and various methods designed to help people extract pose from it, among other things. The same thing needs to be done for the homography matrix.

This should work:

cat test.txt | unic-inspector

I am looking at using ktra as an internal registry at work, and while I don't think I will loose my password, there is the possibility for others to do so. It would be nice to have a way to delete user accounts or forcibly set an account's password to allow for recovery.