For reference, files would be locally on your machine and then also in the “hidden” folder where your IPFS repo is.
We should make all Fission interactions pin files locally, unless explicitly told not to pin.
There’s probably some discussion to be had about not duplicating files into the repo.
This is a good idea. This would make stuff on fission drive available when user is off line.
I would like to tell fission.drive, here is a cid for something I just pinned on my machine,
please make sure that it is pinned on fission drive too.
Thanks again for posting and suggesting! Filed this as an issue:
Pinning or following the IPNS address of drive / an app, like
/ipns/USERNAME.fission.name may also be possible, so whenever your local IPFS node is online it syncs automatically.
I’m doing some research on our cluster approach right now, for distributing IPFS nodes geographically as we discussed in chat. A local / personal node should be able to participate as well.
I currently keep a folder for every different app / drives on my machine. This of course means that files are duplicated, since they are ALSO in the (hidden) IPFS repo. So I’m thinking about how to expose that more directly. That may look more like a FUSE approach, like https://github.com/ipfs/go-ipfs/blob/53739faee019ca29e48a67a818ad56e538025dff/docs/fuse.md
Orion has some intriguing settings:
- Filestore enabled: Allows files to be added without duplicating the space they take up on disk.
- Sharding enabled: Allows to create directories with unlimited number of entries
I would like to build (inter) Personal MindDrives around such a storage across users’s devices that would include something like fission.drive in the cloud
The very act of saving any file there would carry bidirectional meaningful links to the context where any resource is referenced.
I built an exploratory system around Google Docs
and Drive 5 years ago.
Would like build all that on Web 3