You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have a Put and Get, We also need a Rm endpoint for go-fula so that it removes the stored data (which we use IPFS read opener and write opener for read and write at the moment)
For the data store WNFS calls ....tbd... endpoint for removal of cids
The text was updated successfully, but these errors were encountered:
The process for rm in WNFS is that:
It does not remove the cids corresponding the the path but just puts the updated cids in the HAMT without that node. so it only puts some cids and does not remove anything indeed.
So I think a suggested process for rm is that:
1- we find out which cids are get when we request that specific file, check what cids are put after rm is done by WNFS. and request to unpin the ones that are removed and pin the ones that are created. However, in theory we should not charge users for new cids (or should we?). I do not have a process for it on chain side right now in my mind
Currently we have a
Put
andGet
, We also need aRm
endpoint for go-fula so that it removes the stored data (which we use IPFS read opener and write opener for read and write at the moment)For the data store WNFS calls
....tbd...
endpoint for removal of cidsThe text was updated successfully, but these errors were encountered: