Mikeal Rogers

The “compile time” switch would need to be some some kind of configuration in which the developer imports a pure-JS module and passed it into `js-multihashing-async`. There’s no way to...

IMO, the APIs should **accept** any binary type or view and just convert to a `Buffer` internally if necessary. I’d love it if we also never returned `Buffer` instances, but...

> I actually implied getting rid of Buffer although I guess that is probably better set aside for next iteration. The way I was thinking to go about is to...

From a user perspective, matching the loose (case insensitive) rules found elsewhere would allow people to easily take existing base encoded strings, pre-pend a character for the multibase identifier, and...

We want to try and capture all commonly used base encodings, so we should figure out the best way to support this. It is true that *today* some multibase implementations...

i know, but it means we increase the space taken up by the metadata at a much faster rate than varints. i’m also a little worried about using up the...

@vmx I think this (base encodings) is a little different than codecs. There isn’t a gigantic list of prior formats to consider, nor do we expect the list of base...

> Internally, in IPFS/libp2p/IPLD, we use unwrapped, binary multihash, so base does not matter outside userland. *Mostly*, yes. `dag-json` uses base encoded CID’s internally in its format but uses a...

I doubt I'll have time to dive into this before I go on vacation but **this is awesome!**

Is there a broader discussion already about how to square the existing origin based browser security model with the broader IPFS vision of a decentralized web? This is a great...