-
Notifications
You must be signed in to change notification settings - Fork 864
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
Pin files on other nodes #602
Comments
This goes hand-in-hand with interacting with other IPFS daemons from IPFS-Desktop, be it the one installed on the system independent on IPFS-Desktop (e.g., tell the system daemon to pin it) or a remote daemon through its API endpoint. |
As an "end user", I'm interested in such a feature for using IPFS as a backup solution. I would love if I could store stuff (photos, etc.) on my local computer, and have it automatically synchronized (and pinned) to some NAS or something. |
There is a related UX discussion at: ipfs/ipfs-gui#36 |
if pinning is the way to make file links permanent, shouldn't it be part of the adding process by default? |
Will close this issue on this repository and let the discussion flow on ipfs/ipfs-gui#36. We first need to know how to do the whole process before thinking about how to implement it on IPFS Desktop. |
Usually when I add something to IPFS, I add it to my local peer, save the hash, ssh into pollux (one of our storage hosts) and pin the hash there as well.
Would be nice to have this flow supported on ipfs-desktop, as I'm sure I'm not alone in doing this.
I know the focus of ipfs-desktop is currently not on "power users" but to be as user friendly as possible, but opening up this issue for reminding ourselves in the future.
The text was updated successfully, but these errors were encountered: