4 ms·
iroh documents are a work-in-progress implementation of willow: https://github.com/n0-computer/iroh https://github.com/n0-computer/iroh We've been working with
by b_fiive 3y ago
iroh documents are a work-in-progress implementation of willow: https://github.com/n0-computer/iroh https://github.com/n0-computer/iroh
We've been working with the willow team as we go & giving feedback on the spec.
disclosure: I work on iroh.
- elmolino89 3y agoThe iroh name resembles a bit iRODS, another system for distributed file sharing and fine grained permissions. Quick googling did not give me a proper grasp of the use cases for iroh/IPFS vs iRODs. Would you be willing to list the benefits of iroh vs IRODS?
- b_fiive 3y agowow, thank you for pointing me to IRODS, I was not aware of the project! Big difference I'm seeing as I read the docs for IRODs is a datacenter-grade data management _service_, whereas iroh is a multiplatform SDK for building your own applications. Seems like one would want IRODs if they have massive amounts of highly sensitive data that needs fine grained access control. You would want iroh if you're building an app that uses direct connections between end-user devices to scale data sync
- rklaehn 3y agoI was not aware of iRODS. Iroh is named by a certain fictional character that likes tea. Any similarity is a coincidence. But it seems like iRODS is much more high level than iroh. E.g. iroh certainly does not contain anything for workflow automation. You could probably implement something like iRODS using iroh-net and iroh-bytes.
- jw_cook 3y ago> Iroh is named by a certain fictional character that likes tea. "The file was in my sleeve the whole time!"