Could this be used to create a kbfs (keybase file system) competitor?
Yea totally. The FUSE support is already very close to being elexactly that. We’ve been using it internally during our beta as an in office P2P dropbox using the mounts feature
Hyperdrive v10 – a peer-to-peer filesystem
31–40 of 124 posts
Re: Hyperdrive v10 – a peer-to-peer filesystem
#32Been following this for years, congratulations on your release. I looked at dat for building P2P services, but found that ZeroNet was actually more capable for "real" services - maybe now is the time to reevaluate that, especially given the improvements to large (both deep and wide) archives and the new hole punching. Can you please mention your thoughts on: - Discoverability of content in Hyperswarm (DHT Search/"Sup…
Thanks Mizza!
Not sure if I'm answering your first point, but Hyperswarm is baked into the Hyperdrive daemon, so daemon users should have their drives swarmed/available automatically. There are a few CLI commands to toggle this behavior too, in case you don't want to add your drive's key to the DHT.
The Hypercore Protocol org's creating a similar proposal repo called HYP [0] (we couldn't resist the name), scoped tightly to the core protocol. We're still solidifying the proposals plan, but yours would add lots of value, so we don't want to lose track of it.
Since your proposal is about peer identifiers, you might like that Hyperswarm uses the Noise protocol [0] to handshake each connection, and the Noise key can be used as a stable peer ID.
As for use-cases, check out Beaker (launched today too). Paul's made a whole bunch of example applications that take advantage of Hyperdrive features, like drive mounts.
I'm personally really interested in using Beaker to make personal document indexers + search (kinda like an amped-up Dropbox), but that's for another post!
Re: Hyperdrive v10 – a peer-to-peer filesystem
#33Earlier quoted context omitted.
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 :)
this one? https://dumps.wikimedia.org/other/static_html_dumps/current/... how long does it take to import it?
I think it was that one yes. Can’t remember the exact time it took, as we ran it over a couple of days due to some unrelated computer issues.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#34Does it support private clustering and encryption? My use case is to have shared volumes between servers, laptops but without all the networking hassle (VPNs, opening firewalls).
Re: Hyperdrive v10 – a peer-to-peer filesystem
#35what version of node.js does it require? i get this with v10.19.0 from Ubuntu 20.04: node_modules/hyperdrive-daemon/node_modules/hyperdrive-daemon-client/bin/commands/create.js:8 static usage = 'create [path]' ^ SyntaxError: Unexpected token =
Oops, give it a shot in v12. Think static class properties were added after 10.
v12 seams to work, v14 crashed. Would be nice to have that info in the README.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#36> Hyperdrive is a POSIX-like filesystem implementation
How POSIX-like is it?
From a filesystem I would expect some more rigorousness than just stating this without any extra information, especially as implementing an actual, to-spec, fully distrubuted POSIX file system is known to be a difficult problem and is generally solved by not wanting a full POSIX-compatible implementation instead (ie. no locking, append-only files, etc.).
Re: Hyperdrive v10 – a peer-to-peer filesystem
#37Does it support private clustering and encryption? My use case is to have shared volumes between servers, laptops but without all the networking hassle (VPNs, opening firewalls).
It uses Noise to encrypt all transport connections and using the api you can whitelist which peers (by their public key) you want to replicate with. This API is not yet exposed through the daemon but it’s in the modules.
Hyperdrives also have a built in capability system where you have to know the public key of the drive to download it from a peer, so if you only share the key with yourself no one else can access it.
Finally using the modules you can build almost any kind of networking you’d imagine but that part requires more work on your side obviously.
Re: Hyperdrive v10 – a peer-to-peer filesystem
#38Re: Hyperdrive v10 – a peer-to-peer filesystem
#39I've been following dat since a few years and I've been hearing about multiwriter since a few years but not anymore.
Is it still something you are working on ?
Re: Hyperdrive v10 – a peer-to-peer filesystem
#40Earlier quoted context omitted.
v12 seams to work, v14 crashed. Would be nice to have that info in the README.
It should work on 14. Could you open an issue on the repository?
filed hyperdrive-daemon #47 problem with hyperdrive-daemon/node_modules/fuse-native/prebuilds/linux-x64/node.napi.node