Hyperdrive v10 – a peer-to-peer filesystem
blog.hypercore-protocol.org
Hyperdrive v10 – a peer-to-peer filesystem
1–10 of 124 posts
Re: Hyperdrive v10 – a peer-to-peer filesystem
#2Hyperdrive is part of the peer-to-peer networking stack that Beaker Browser uses for websites. Today is release day and this tech update is the first announcement.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#3What are the main differences between this and Syncthing?
Re: Hyperdrive v10 – a peer-to-peer filesystem
#4What are the main differences between this and Syncthing?
I'm not deeply familiar with Syncthing but here are some differences based on what I do know:
- Hyperdrive includes mass-publishing as a usecase, so it uses public-key URLs and a bandwidth-sharing mechanism among its active peers (like BitTorrent)
- Hyperdrive is built on a general-purpose protocol called Hypercore which is a signed append-only log. These logs can be used for other datastructures. Some examples [1] [2]
[1] Kappa-core, a general-purpose db built on the logs https://github.com/kappa-db/kappa-core
[2] Cabal, a chat network https://cabal.chat/
Re: Hyperdrive v10 – a peer-to-peer filesystem
#5Color me interested. I've been wanting to use IPFS for similar use case but there's always something that annoys me or documentation that's lacking.
While reading Hyperdrive/Hyperswarm docs I actually managed to find everything I wanted to know without much effort (most of all it seems like setting up this on private network should be doable)
Re: Hyperdrive v10 – a peer-to-peer filesystem
#6Total noob question, but:
Last time Dat was on HN I tried to follow the "simple chat application" tutorial[0], but got stuck at the stage where 2 instances were supposed to automatically discover each other because they only intermittently managed to actually discover each other.
Will this new version of Hyperdrive improve this? Or is it something completely different?
Re: Hyperdrive v10 – a peer-to-peer filesystem
#7Hyperdrive is part of the peer-to-peer networking stack that Beaker Browser uses for websites. Today is release day and this tech update is the first announcement.
What is your relationship with Hyperdrive & the Beaker Browser?
Re: Hyperdrive v10 – a peer-to-peer filesystem
#8Congratulations to the team !
2 questions:
- What is the difference between dat and hyperdrive ?
- I see hyperdrive manages hyper:// urls -- what about dat:// urls ? Will they be still managed ?
Re: Hyperdrive v10 – a peer-to-peer filesystem
#9I'm not able to view the link due to HTTPS errors.
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#10Total noob question, but: Last time Dat was on HN I tried to follow the "simple chat application" tutorial[0], but got stuck at the stage where 2 instances were supposed to automatically discover each other because they only intermittently managed to actually discover each other. Will this new version of Hyperdrive improve this? Or is it something completely different? [0] https://docs.dat.foundation/docs/kappa
The new version has a totally revamped networking stack that should be a lot faster and more reliable. Part of it includes a new UDP holepunching algorithm that's had a super high success rate for us in practice.
There are some diagrams describing this on the Hypercore Protocol [0] site, and the repo's can be found here.