Stebalien
commented
6 years ago We can almost do parts of this, it's just really buggy. You can mount /ipns and read/write to /ipns/local. This will even update your IPNS address to point to the latest version of the directory.
However, it's really buggy and slow.
But yeah, many of us have been wanting to do this for a while.
IvanTurgenev
So any app can use it? when a file is written to the fuse ipfs mount quickly add it(make some kind of cache if ipfs add is not fast enough), when it gets deleted ipfs unpins it, when disk gets full runs the GC to delete unpinned files.
This will also avoid having duplicated files the original copy and the cached ipfs version as we all are to familiar with.
The root of the mount point is off course an ipfs folder. Modifications return a new folder, but for the fuse file system it will seem as if nothing happened, the folder appears the same but with the modifications.
Encrypt personal files, this has to do more with ipfs implementation, if a user decides to sync multiple folders on multiples nodes add a way to associate that file/folder with a user maybe a user password file sign thing, so the user has folders in sync on multiple nodes. Within this folders differentiate between personal and public files so not everything gets encrypted and deduplication gets lost(as most heavy data is common between us), only personal files get encrypted, but the syncing still works for the user, meaning add a way to securely sync but the public data will still be public, to help the network.
Files off course will have their filenames locally on the fuse but they will still have the same hash also when a file gets share, it will keep the filename it was shared with, also as i said earlier when a user has two folders in sync in two different machines modify the name of the files if the user changes it on one of his synced folders.
If i have two nodes and one node runs out of space on the fuse filesystem it wont matter as the files would still be visible on the node that ran out of space, because it exists on the other node, or possibly, in other peoples nodes also, so it will still be visible and transparent to apps
Delta file transfer, constantly changing files ¿? for example when i download a torrent to a synced folder automatically send files pieces as it gets downloaded to the other synced folders.
Add a way to avoid file conflcts on synced folders.
Mount the whole¿? install my operating system on the ipfs
I cant think of a more practical use, also in this fuse mountpoint ad a way to quickly get the file/folder hash, so everything is transparent and easy to use.
Randoms thoughts, but this way people wont be constantly asking what ipfs can do for me(aka i dont want ipfs get add for everything i cant live on the command line file by file, 0 practicality also having to keep the original copies), as i said for everyone it will be transparent but the benefits would be huge, i hope yall understood me