New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
storage driver for IPFS #438
Conversation
@jcnelson In IPFS there is no way to actually delete data from the network once published, especially for the immutable data (for mutable you can delete the pointer to it). Are you suggesting that we should design the driver in such a way that Blockstack thinks that data is deleted but in reality is still reachable by the underlying IPFS? |
Thank you for your submission! I'll take a look today.
Yes, this is sufficient. |
@jcnelson Checking in for an update on this. Thanks! |
Hey @sunnya97, sorry this got away from us. So far it looks good! I'll take a look at it tonight and let @shea256 and @muneeb-ali know. |
Hey @sunnya97, I ran the tests described in the issue. I'm not sure why this is happening. Maybe you can shed some light?
My IPFS daemon is running. It's output is:
|
Proposed storage driver for IPFS in response to #430
Before using, you will need to use pip to install ipfsapi.
You will also need a local running instance of IPFS.
Uses the ipfs MFS for mutable files.