2 ms·

At Fission, we built a library called WebNative File System[1] that effectively solves exactly this problem: every user gets their own file system stored in IPF

At Fission, we built a library called WebNative File System[1] that effectively solves exactly this problem: every user gets their own file system stored in IPFS[2]. I've been building a few apps with WNFS over the past few months. It's a mind-bending architectural model coming from client-server architecture, but it has some clearly superior qualities, as you point out in your documentation. Feel free to swing by the Fission Discord if you want to talk about it[3]. [1] https://guide.fission.codes/developers/webnative/file-system-wnfs https://guide.fission.codes/developers/webnative/file-system... [2] https://ipfs.io/ https://ipfs.io/ [3] https://fission.codes/discord https://fission.codes/discord

Rygian 4y ago
Thanks for sharing, awesome work! Indeed, this has some similarities to the problem I'm addressing. I wouldn't go as far as saying it "solves exactly the problem." A couple of points where it diverges: it is backed by IPFS, so the user does not know and cannot decide where their data is physically stored — I consider this as a requirement. Another requirement, which I agree is more on the utopia side of the spectrum, is that all my devices (as a regular user) should use WNFS for all my user content by default, at the OS level (rather than me having to use dedicated applications that support WNFS). Reliance on IPFS, rather than a local-first approach, would be a blocker for this kind of low-level integration. The very interesting parts for me are the DAG representation for the filesystem and the versioning capability (which comes naturally through IPFS, I guess).