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

It is a very exciting Authorization Flow for developers of server-less applications that use Spotify API directly.

Not only will the users of these applications no longer have to setup their own Spotify Applications,
but also the creators will get to see usage metrics of their applications in their Spotify Dashboard.

You can find out how it works [here](https://developer.spotify.com

This should work:

cat test.txt | unic-inspector

from conversation with @sunshowers

fn filter<F: FnMut(&PackageMetadata) -> bool>(&self, f: F) -> Self

This can be accomplished using intersection, but it would be great to have a convenience function for it

you could also add a parfilter function that uses rayon

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.

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.