Creating an IPFS UnixFS File System By Hand
I am contemplating a collaborative file system based on IPFS. Users will publish the root of a directory tree & a service worker will copy that tree into a Neo4j instance running in Docker with a model of a versioned repository in it.
The frontend, then, will talk to Neo4j (which is a graph database) to allow more complex views of the data than a simple tree view.
I'm particularly interested in incorporating ordered lists where users rank content. Say I could get 50 people's opinions of the top 20 funniest memes ever, & generate a composite list from those.
To avoid having to upload a ton of information for every update, I want to reuse the unchanged parts of the previous iteration that are already in IPFS rather than reupload.
To do this, I need to manually construct the directory tree. I had it working with a CBOR-DAG, but the
ipfs dag
commands are only available on instances where you have API access. So, I want to switch to UnixFS to store stuff.
I've tried to get Claude, V0, Co-Pilot, & Bolt to help me, and this is where we're at currently:
The output I get from that is:
So, my file attempt has a bunch of random crap in with the data, & my directory doesn't have any children. When I open either up in the IPFS Desktop it says they're not browsable.0 Replies