It'd be great to have an even more robust fuzzer for snow to increase confidence and avoid panics.

Could the crate documentation be updated to specify what the exact bounds on noise output values are? Experimentally, two-dimensional OpenSimplex noise values appear to always lie in the range [-0.544, 0.544].

Related: #51

Currently, handshake patterns with I and X (key is transmitted as part of the handshake) seem to enforce signatures and a PKI. For example NX:

Noise_NX is a handshake pattern similar to a typical browser ↔ HTTPS server scenario where the client does not authenticate itself and the server authenticates its public key via a signature from an aut

Please help in translating Noice to your local language.

Note: _Even if translations for your local language exist in Noice, it is a good idea to revisit them. The project is always under development and translations are lagging behind. If you have Android Studio environment setup on your local machine, clone the repository and take a look at values/strings.xml. Android Lint will highligh

Would be good to have an option for all plots that allows to add a bottom line with creation info (timestamp and/or copyright) on the figures.

In routine, it's then easy to check if the figure is the latest version / if run fails.

I tend to think that beta1 and beta2 are off. I think that beta1=0.4 and beta2=0.1 may be better defaults than what we have right now, but this would need extensive testing. That's a very high gain but right now we rarely ever reject, and are usually 10-100x below the error estimate we are aiming for.

The urls used in the code and documentation should be checked for availability (As done for the readme in #87)

Places to check:

• URLs in the CorpusDownloader classes
• URLs in the code-doc of CorpusReader classes