31 lines
1.5 KiB
Markdown
31 lines
1.5 KiB
Markdown
# iotaFS
|
|
|
|
A FUSE-based FS that stores your stuff on the IOTA-Tangle (comparable to the Bitcoin Blockchain) for free! (Well, you pay with POW...)
|
|
|
|
## main.py
|
|
|
|
Fully functional poc, but has horrible performance.
|
|
|
|
|
|
## next.py
|
|
|
|
Non yet functional and I'm also no longer working on it.
|
|
Changes compared to main.py:
|
|
- switched to libfuse3
|
|
- switched to a async model
|
|
- switched to object-oriented class-structure
|
|
- switched to a way more efficient delta & milestone system
|
|
- appending data to files without a re-upload possible, if file has not been closed
|
|
(and therefore the last block is still unsealed)
|
|
- incremental r/w-keypair in directory-structure: mounting point in the fs can be choosen and a single folder (and all contained files / folders ) can be shared with someone else simply by giving them the r/w-keypair and last known milestone-pointer (address) for the folder
|
|
- sharing a folder in read-only mode by only giving them the r-key and the last known milestone-pointer
|
|
- did I mention it has 1000x better performance?
|
|
|
|
Development was stopped, because a iota-snapshot will remove the fs (next AND main) from the tangle and require the data to be bought from a fullnode.
|
|
If a transitional grace-period for snaphots gets implemented this could be circumvented by implementing a refresh, which would
|
|
|
|
- make a forced full milestone of the Genesis
|
|
- rewrite all files
|
|
|
|
But until such a thing is implemented I dont see the point in continuing the development on what essentially was only ment to be a poc.
|