Indicate byte array inputs are supported too

[shesek]

I was going to write a wrapper function in my application that adds support for that, but noticed that it already does support that - the input is processed by bytesToWords, which works well with byte arrays. I updated the README to indicate that.

One other thing that should perhaps be looked into is the different APIs that the SHA256 and RIPEMD160 modules expose. SHA256 can return multiple formats, but doesn't support Buffers, while RIPEMD160 only returns buffers. It probably makes sense to unify the interfaces (imho, I think its best to always return buffers and let the user handle other formats in app-land), but it'll probably break some code that depends on that.

[jprichardson]

Thanks for the contribution. The module sha256 is deprecated. The long-term strategy is for us to "outsource" most of the crypto to browserify (https://github.com/dominictarr/crypto-browserify specifically). It includes sha256 functionality, but not ripemd160 functionality. To mitigate all of this, we've been using the module crypto-hashing to normalize interfaces.

[shesek]

Yeah, I got the feeling that crypto-hashing is what you're aiming to use as the primary API and ended up using it as well. Perhaps you should add a deprecation note to the README?