Why did you pick Hypercore to build Slashtags upon instead of much better supported projects like IPFS/libp2p or ION/IdentityHub/DIF?
These two competitors offer similar set of functionalities and they're being actively being developed by big teams of experienced people and are supported by millions in funding. Do you think they are all wrong?
We chose Hypercore for several reasons:
  • This video clip:
  • It offers a way to do blockchain-like things without using a blockchain because it uses append-only logs
  • We are friends with one of the main teams that works on it (Holepunch, formerly Hyperdivision, incl Mathias, the guy in the video above) and thus able to help each other regularly with using it.
  • IPFS is tied to a scamcoin, but even then we have actually used some tools from those devs within our work too.
  • Our vision and design for the next web requires a design like Hypercore and the ability to have integrity yet flexibility. Hypercore will become the clear winner after you see the next round of tools being deployed this summer from Holepunch and Synonym.
  • Yes, I think IPFS and ION are "wrong", yet we will all converge on certain aspects in our designs, because I believe there is actually only one optimal design we are all iterating towards. I firmly believe there is no need for a blockchain for any dweb/identity things, thus ION using Bitcoin feels forced and gimmicky. They make the argument that blockchain provides confident key-rolling through block broadcasting but this assumes master keys are not compromised, which is a bad assumption imo. Plus, Slashtags could use the blockchain anytime if we really wanted, we just think Hypercore makes a lot more sense.
  • Regardless of team-size or community, we do not want technical debt or inferior designs. We believe that once our teams deploy our first products and platforms that utilize Slashtags & Hypercore, we will create plenty of gravity for our stack.
reply