Conversation

Arguably things are even worse than discussed in that article. Take Firebase, for instance: it implements offline caching, but that's very different from sync. You have to design a whole replication strategy on top to get something like "a synced file format."

5:44 PM · May 15, 2021TweetDeck

CouchDB seems like the closest solution, if you can design a conflict-free model. But I spent the last week getting into the details of actually operating a multi-user service, and I am now quite thoroughly spooked!

try

Replying to

and

Both new to me, thanks—will read up.

Replying to

and

thanks

. Founder of

here Andy 👋 We designed a file system on top of IPFS, this is a presentation that goes into detail blog.fission.codes/web-native-fil We’re participating with the

@DecentralizedID

to work on personal data store standards

fission.codes

Web Native File System Technical Design Overview – Fission

Brooklyn and Daniel from the Fission team present a technical overview of the Web Native File System.

Thanks! I'm very excited about the distributed design direction. Unfortunately a file system doesn't quite fit my application model: I'd still need to build a database on top of this for querying/indexing. I see there's a TODO for databases in the white paper?

Show replies

Replying to

and

some examples of how these work at the moment: 0data.app/glance/ i work on hyperdraft to joybox