I'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.
That's odd, what browser?
Hyperdrive v10 – a peer-to-peer filesystem
11–20 of 124 posts
Re: Hyperdrive v10 – a peer-to-peer filesystem
#12Total 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. [0] https://hypercore-protocol.org/#hyperswarm [1] https://github.com/hyperswarm/hyperswarm
The new holepunching algorithm also runs distributed on the our DHT, meaning any peer can help you holepunch to other peers.
We also talk a bit more about this on the hypercore website
Re: Hyperdrive v10 – a peer-to-peer filesystem
#13Congratulations 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 ?
Thanks!
- "Hyperdrive" was formerly the internal data-structure name of Dat archives. With this release, the team decided to rename the protocol from Dat to Hypercore Protocol. Subsequently, "Dat Archives" are now "Hyperdrives." The Dat community will post some updates about this soon.
- The hyperdrive-daemon does not support dat:// URLs. I don't know what the future of dat:// URLs will be but Beaker is phasing them out with a converter tool.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#14> written in Node.js
Yeah. No, thanks.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#15Oh dude, I'm sorry but I read
> Hyperdrive is a POSIX-compatible filesystem implementation, written in Node.js
And just cracked up! Thanks, I needed that.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#16Oh dude, I'm sorry but I read > Hyperdrive is a POSIX-compatible filesystem implementation, written in Node.js And just cracked up! Thanks, I needed that.
Fair enough -- updated it to POSIX-like. The main point there being that it should be as straightforward to use as Node's fs module.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#17does it scale now?
previously i was not able to import large folders (several TB) or many files (+100k files)
Re: Hyperdrive v10 – a peer-to-peer filesystem
#18[deleted]
Re: Hyperdrive v10 – a peer-to-peer filesystem
#19> written in Node.js Yeah. No, thanks.
Wow. What a way to describe the tradeoff of a programming language. No, thanks
Re: Hyperdrive v10 – a peer-to-peer filesystem
#20does it scale now? previously i was not able to import large folders (several TB) or many files (+100k files)
Yep! That is one of the things we’ve worked the hardest on. Completely new indexing structure, using an append-only hash trie which scales really well. We’ve tested it with many big datasets including importing all of Wikipedia as files in a single folder. Worked like a charm :)