Tahoe-LAFS VS ipfs

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.

> CDNs

If you think IPFS is trying to "re-spin CDNs as their invention", I'm pretty sure you misunderstand what IPFS. The homepage is a great starting point if you're curious rather than antagonistic: https://ipfs.tech/

> IPFS doesn't solve persistence of data

I don't think it claims to solve this either? What it does claim to solve is the persistence of identifiers of data.

> doesn't solve churn in p2p systems

What P2P system has ever done so or even claimed to have done so?

We will create a web app that will let users mint a NFT in one click: creating an AI art from a prompt, storing it on IPFS and mint the unique NFT in Polygon so you can see it on OpenSea. Pretty cool right ?

IPFS, which stands for Inter-Planetary File System, is a decentralized storage system where files are distributed among peers in a peer-to-peer (P2P) network. It operates on a "content addressable" model, meaning that each file is given a unique hash that serves as its identifier. By using this hash, you can retrieve any file from any IPFS node in the network.

Like this? https://ipfs.tech/

Was thinking of something and figured it would be a good opportunity to ask here. With the censorship madness going on in the world and furry community included, I often worry if even places like e621 can remain free and open in the face of increasing pressure by increasingly angry and authoritarian crowds. For both this and other geek reasons I've been interested in decentralized internet technology for a long time, following projects like IFPS which I just love as a concept.

Using the Interplanetary File System, a real thing that exists today, designed for this purpose.

I post a lot about IPFS, I was using the 'ipfs mount' to virtually offer my entire collection from my NAS (on a private 'swarm' of course) to the remote stations.