IPNS mount, <MISSING> writing a file being fetched to the mount point
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
#### Version information:
#### Type:
Bug
#### Description:
I have made some progress in fixing the bugs in IPNS mount. Specifically, as far as I know, there are two issues currently:
1) IPNS address is not resolved correctly.
2) The files being fetched from peers through the mount point are not written to the IPNS mount point.
For the first issue, I was able to identify and fix the issue. I will create a pull request so that the fix can be incorporated.
For the second issue, I am not sure how to implement it.
I would think the following to be the desired behavior of the IPNS mount point:
1) When a directory/file/tar is fetched from peers through the IPNS mount point, the file should be written under a new directory, whose name is that of peer-id (/ipns/PEER_ID/directory>.
2) This directory/file/tar should have the option to be edited locally. For example, if it is a directory, new files can be added or old files can be deleted. If it is a file, the user should be able to make changes locally to the file.
Any thoughts on how this should be implemented?
Contributor guide
Assessment
This issue has not been assessed yet.