ipfs VS orbitdb

> 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.

OrbitDB is not well-funded, but there's fresh work happening recently by some dedicated volunteers: https://github.com/orbitdb/orbitdb/commits/main

I've been thinking it might be practical to build a simple decentralized database, where agents just know each other, so conflict resolution does not need to be so strong and can rely on the social layer.

I think this applies to most databases, but I'm particularly thinking of internal enterprise databases, some social networks, any federated database system, and different devices of a single user

I'm thinking of this features:

1- Append-only?, full history of operations. Deletes / edits do not remove data, they only modify the "active state"

2- Agents are public keys or similar (DIDs?)

3- Operations are signed, and receivers verify if operation is valid, and sender is allowed

4- Operations form a Merkel-DAG (similar to git, they link to the tips of current "active state", like a commit/merge in git)

So far I think I've basically described [OrbitDB](https://github.com/orbitdb/orbit-db)

Consensus is where things get real hard, [OrbitDb seems to use a last-write-wins CRDT](https://news.ycombinator.com/item?id=22920204), and although I don't know the details of orbitDb, I think for many simple use-cases, conflicts can just be resolved on the social layer. But I think we need to provide agents with good tools to resolve conflicts

I'll try my best here with some ideas:

- When merging, we can order operations by their timestamp, if operations enter conflict, raise it to the conflicting agents, or someone with permission to solve them.

If an agent makes public an operation that forks its own history, mark agent as malicious or compromised, alert other agents, this needs resolution on the social layer, you have proof of misconduct, an agent has signed diverging operations

Any operation becomes fully settled if you have proof that all agents of your system have referenced it directly or indirectly through newer operations.

Timestamps can be upgraded by using @opentimestamps to get proof that an operation existed at time X (prevents creation of operations in hindsight). Though this does not prove operation has been made public

Both use OrbitDB: Peer-to-Peer Databases for the Decentralized Web. JavaScript. MIT license. repo

I think a wallet-agnostic memo solution is definitely the way. Having wallets that end up (partly) incompatible is only gonna hurt the UX. Maybe a decentralised DB solution like OrbitDB or GunDB can be the best way forward, although I haven't dove deeply into the docs yet.

Checkout this https://github.com/orbitdb/orbit-db peer-to-peer database for the decentralized Web.