First, thank you for IPFS, it seems to be a definitely fun and perhaps promising idea :-)
Any document is dynamic most of the time: its URL can change and so can its content itself. IPFS hashes solves the first part but how can we retrieve the latest available version of a document?
To the best of my knowledge, tree-based version control system (such as git) makes it trivial to access to parents of a document but further revisions are less easily accessible.
The text was updated successfully, but these errors were encountered:
The IPNS (InterPlanetary Name Space) solves the issue of accessing the latest document. It is described near the end of the IPFS white paper.
Every user is assigned a namespace at /ipns/<NodeId>. Then a user can put new files at places underneath this, like /ipns/<NodeId>/cat.gif, which would link to a IPFS content address in its metadata.
piotr-yuxuan commentedOct 28, 2016
First, thank you for IPFS, it seems to be a definitely fun and perhaps promising idea :-)
Any document is dynamic most of the time: its URL can change and so can its content itself. IPFS hashes solves the first part but how can we retrieve the latest available version of a document?
To the best of my knowledge, tree-based version control system (such as git) makes it trivial to access to parents of a document but further revisions are less easily accessible.
The text was updated successfully, but these errors were encountered: