A deny.toml without an [advisories] section will still check the RustSec when running cargo deny check advisories. This is great and the correct behaviour imo, but it would be good to document the default value for all configuration option and afaict it is not.

Thanks! :)

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 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

This should work:

cat test.txt | unic-inspector

As nice as it is to be able to remove the blatantly bad stuff, sometimes you don't want the user to be able to enter any HTML at all. You could do this by escaping the markup, but if having a database with < in it doesn't appeal to you, or you're worried about double-escaping or similarly nasty accidents, you could use a function that just tells you if a string has any HTML tags in it. And in

Currently it's an Option<&[String]>, which is kind of ugly. Instead, we should return an enum that's something like:

enum PackagePublish<'g> {
    Disallowed,
    Registries(&'g [String]),
    Unrestricted,
}

cc @bmwill

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.