4 ms·

Sound to me like Tahoe-LAFS [0] on global scale. Shall we build this ? https://tahoe-lafs.org/trac/tahoe-lafs https://tahoe-lafs.org/trac/tahoe-lafs

by rakoo 13y ago

xiaomai 13y ago
I was under the impression that Tahoe-LAFS doesn't work offline. Is that not the case?
- rakoo 13y ago
  Indeed, but Tahoe-LAFS is not a replacement for your filesystem, rather a virtual place to backup and share files. Common use would be to have all files local, and a copy on your Tahoe-LAFS swarm.
foobarqux 13y ago
You need to run special gateway servers, I don't think it uses transparent encryption and there isn't a global namespace (for sharing publicly or with non-static groups).
- rakoo 13y ago
  First, more reading: https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/about.rst https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/ab... > You need to run special gateway servers You don't _need_ to, each peer can run its own gateway on localhost. Gateway servers are useful if you're on a computer where you can't install anything. > I don't think it uses transparent encryption I'm not sure what you mean by that, but if it means you need to manually encrypt things before storing it in tahoe-lafs, you're wrong. The whole point of Tahoe-LAFS is to push your files to it, and it will automatically encrypt, erasure-encode and distribute it to all nodes in the swarm you're in. All you need to care about are URIs returned by Tahoe-LAFS, and which contain all you need to use files (no need for extra password or keys, in fact they're contained in the URIs) > there isn't a global namespace Tahoe-LAFS swarms are defined by their introducers, the central piece that ties all storage nodes and potential clients together, kind of like a bittorrent tracker. There are no namespaces because swarms are not globally defined (although a node can take part in multiple swarms, this is completely invisible from Tahoe-LAFS users. Exactly like bittorrent). My proposition was to build a world-level swarm, where anybody could register and participate in the swarm. If you wonder about the reliability of a central introducer, there is work in the pipes for creating decentralized introducers.

Sound to me like Tahoe-LAFS [0] on global scale. Shall we build this ? https://tahoe-lafs.org/trac/tahoe-lafs https://tahoe-lafs.org/trac/tahoe-lafs

by rakoo 13y ago

Sound to me like Tahoe-LAFS [0] on global scale. Shall we build this ? https://tahoe-lafs.org/trac/tahoe-lafs https://tahoe-lafs.org/trac/tahoe-lafs

xiaomai 13y ago

I was under the impression that Tahoe-LAFS doesn't work offline. Is that not the case?

rakoo 13y ago
Indeed, but Tahoe-LAFS is not a replacement for your filesystem, rather a virtual place to backup and share files. Common use would be to have all files local, and a copy on your Tahoe-LAFS swarm.

foobarqux 13y ago

You need to run special gateway servers, I don't think it uses transparent encryption and there isn't a global namespace (for sharing publicly or with non-static groups).

rakoo 13y ago
First, more reading: https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/about.rst https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/ab... > You need to run special gateway servers You don't _need_ to, each peer can run its own gateway on localhost. Gateway servers are useful if you're on a computer where you can't install anything. > I don't think it uses transparent encryption I'm not sure what you mean by that, but if it means you need to manually encrypt things before storing it in tahoe-lafs, you're wrong. The whole point of Tahoe-LAFS is to push your files to it, and it will automatically encrypt, erasure-encode and distribute it to all nodes in the swarm you're in. All you need to care about are URIs returned by Tahoe-LAFS, and which contain all you need to use files (no need for extra password or keys, in fact they're contained in the URIs) > there isn't a global namespace Tahoe-LAFS swarms are defined by their introducers, the central piece that ties all storage nodes and potential clients together, kind of like a bittorrent tracker. There are no namespaces because swarms are not globally defined (although a node can take part in multiple swarms, this is completely invisible from Tahoe-LAFS users. Exactly like bittorrent). My proposition was to build a world-level swarm, where anybody could register and participate in the swarm. If you wonder about the reliability of a central introducer, there is work in the pipes for creating decentralized introducers.