Soni L.

case in point: https://github.com/WebAssembly/wabt/pull/1836#issuecomment-1047951485

Still too monolithic. Crypto crates should also be independent.

Yes, separate repository, and less shared dependencies. If you want to maintain it alone, sure, it would be extremely difficult. The right way is to get someone else to maintain...

It would be best if we had more *different* ppl working on bite-sized bits of crypto. Bite-sized codebases are easier for interested parties to analyze, it would also encourage users...

Python gets it right. There's a hash module and it just calls to external stuff. Granted by default the only external stuff it calls to is openssl, but I'd argue...

Well I did say "config option" :>

many networks support SASL EXTERNAL. whether they'll take SRP or CertFP is another story, and not defined by any RFCs. (neither IRCv3 nor SASL EXTERNAL define it.) I strongly recommend...

So how do you use base128 scripts with this?

They send all bytes > 0x7F. So they can use a full 7 bits per byte. It works great today.

Yes, why break perfectly good stuff that's more efficient than the alternatives?