seaweedfs VS Tahoe-LAFS

Whoops: WebDAV:

https://news.ycombinator.com/item?id=39417503

SeaweedFS supports WebDAV. https://github.com/seaweedfs/seaweedfs/wiki/WebDAV

I'm not able to find if both/restic supports mounting backups as WebDAV, but in theory there's nothing stopping you.

It's 100% user space (expose a rest service) and supported by a bunch of file-browsers with a bit of a network aware component to it as well.

If you want/need to take out the metadata, there's some nice solutions for that https://github.com/seaweedfs/seaweedfs

I posted this on https://github.com/seaweedfs/seaweedfs/discussions/5290

I like the idea of using SeaweedFS as an intermediate layer with object write notifications going to SQS, RabbitMQ, or a local file, which could also allow me to observe the changes to different files through a metric collection layer like Prometheus and Grafana.

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet.

Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing

I've actually been looking for more open alternatives, but haven't found much.

Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively: https://github.com/scality/cloudserver/issues/4986 (their Docker images on DockerHub were last updated 10 months ago, which is what the homepage links to; blog doesn't seem active since 2019, forums don't have much going on, despite some action on GitHub still)

There was also Garage, but that one is also AGPL v3: https://garagehq.deuxfleurs.fr/

The closest I got was discovering that SeaweedFS has an S3 compatible mode: https://github.com/seaweedfs/seaweedfs

SeaweedFS S3 Gateway for Joplin notes

You could also look at Tahoe-LAFS which I keep meaning to try: https://tahoe-lafs.org/

Then there are Darcs and Pijul, which use a theory of patches.

So Pijul manages to have lossless merges by actually storing a directed graph (though of course, you will still need to decide how to flatten that into a displayed file) :

https://jneem.github.io/pijul/

And because uses more information about the history, it is able to do smarter merges (if I am not mistaken, even compared to the OP ?) :

https://tahoe-lafs.org/~zooko/badmerge/simple.html

https://pijul.org/faq

Good news for you: I'm well on the way to solving the problem of better code merging. Specifically, the algorithms I am developing appear to be able to do a correct merge on both [1] and [2]. They also appear capable of merging binary data.

The tradeoff is that people need to write some code to tell the VCS about the format of each binary file type or semantics of each programming language.

The biggest problem is that, like Rust, a new VCS has to be well-executed to make its innovation stick. We'll see if I succeed.

[1]: https://tahoe-lafs.org/~zooko/badmerge/simple.html

[2]: https://tahoe-lafs.org/~zooko/badmerge/concrete-bad-semantic...

u/nextale shared a couple options: Tahoe-LAFS , Duplicati an Retroshare

Only thing that comes close is https://tahoe-lafs.org

There is Tahoe-LAFS which is decentralized open-source software where you can add remote storage servers (for example on a friends server) to store your data but the server does not have the encryption keys. Your data is encrypted before it leaves your computer (they call it "Least Authority File System" or LAFS because only you hold the keys, the storage servers just store the data). The data is encrypted in-transit and on-rest and supports multiple nodes so even if one of the servers burn down you still have the same data elsewhere. I believe they offer a commercial storage solution but you and your friends could install it for yourselves and run a closed network.

do you know https://tahoe-lafs.org? your goals sound similar.