> 1) I wonder why this wasn't written in a language that can compile to wasm, so it could be used on both native and js without reimplementing. The most straig

> 1) I wonder why this wasn't written in a language that can compile to wasm, so it could be used on both native and js without reimplementing. The most straightforward answer is, I extracted this out of an existing project I've been working on: https://rarepress.org/ https://rarepress.org/ I had to build a system that makes use of IPFS without having to publish everything to the public network, and this was where the idea came from. But the "IPFS-Less IPFS" turned out to be much more powerful idea than I originally thought, so decided to turn it into its own open source project. That said, I think it shouldn't be difficult to implement this using Go at some point if this approach becomes popular. For now I wanted to keep the initiative minimal so I can move fast. > 2) Can someone contrast hypercore and IPFS? This is a great question in this context. Hypercore is more focused on the networking aspect, but IPFS is not just a networking protocol but also a way to represent files using immutable identifiers (content addressable file system). What I just did with Nebulus is unbundle the "file system" from the "network" so we can use IPFS in more flexible manner. Speaking of Hypercore, because Nebulus unbundles the network aspect of IPFS from the content addressable file system aspect, it is possible to use ANY network transport to replicate IPFS files, which includes Hypercore.