-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Proposal for deletion mechanism #156
Comments
ipfs is a trustless system. you can't trust any other node in the network to respect your request that they delete some content. Any other node can hold onto data for as long as they please, and you can't prevent that from happening. Unfortunately (for some), a deletion mechanism is not practical. |
Storing unneeded resources isn't really that much of an issue because unused and unwanted resources will slowly be removed from people's caches. Any wanted data is pinned it so it when be deleted when cleaning out the cache. |
Doesn't ipfs has remove file function? Like the add function but reverse? |
Yes, IPFS has a remove function. It only modified the local files you have control over. It doesn't hack into other IPFS nodes and remove their files. |
Related discussion on the FAQ -- ipfs-inactive/faq#9 more there. not here. |
As IPFS becomes more popular and is used for storing larger files it might stand to reason that one eventually has to delete data otherwise people might end up storing data that nobody needs or knows about.
But if anybody can delete a file off IPFS, it would make the job of the censors much easier. Hence I propose that only the person who added the file to IPFS in the first place should have the ability/right to send a signal to nodes to delete the no longer needed blocks. This shouldn't be too hard to do with keys and signing mechanisms out there.
The text was updated successfully, but these errors were encountered: