This is my attempt at creating a prototype of a decentralized store-agnostic file system. More importantly, it runs over HTTP, making it very easy to deploy.
I've been using it for a few days now, mainly for backups and easy access across some of my folders (Video Game Saves, Pictures, ..) on my local network.
It is very similar to a peer-to-peer sharing system, but you almost never know exactly which user created which data. It is simply there.
It enables file sharing across a network of nodes, each node will simply synchronize its state from a peer.
stop50 · 3h ago
It reminds me of syncthing.
michael-0acf4 · 2h ago
Yes! Good point.
I've been using Syncthing for a while too, but my main issue was that it's really hard to express a network of nodes with it. Both locally (on the same machine) and across the network. For example, setting up a topology like A <--> B --> C <--> D ends up being more painful than it should be while allowing some nodes to be on the same machine.
I've been reading about consensus algorithms too, which got me interested in tackling this problem myself and try making it as simple as possible mainly out of curiosity. Also, this project is designed to be storage-agnostic from the get-go (s3 is on the way).
I've been using it for a few days now, mainly for backups and easy access across some of my folders (Video Game Saves, Pictures, ..) on my local network.
It is very similar to a peer-to-peer sharing system, but you almost never know exactly which user created which data. It is simply there. It enables file sharing across a network of nodes, each node will simply synchronize its state from a peer.
I've been using Syncthing for a while too, but my main issue was that it's really hard to express a network of nodes with it. Both locally (on the same machine) and across the network. For example, setting up a topology like A <--> B --> C <--> D ends up being more painful than it should be while allowing some nodes to be on the same machine.
I've been reading about consensus algorithms too, which got me interested in tackling this problem myself and try making it as simple as possible mainly out of curiosity. Also, this project is designed to be storage-agnostic from the get-go (s3 is on the way).