I have been using IPFS for a few days and I do see potential for it, but there are some things that discourage me.
For example when I add a file to IPFS, first I either
ipfs add -r directory or
ipfs add -w file (to get it in a directory and save the filename) and then
ipfs pin add <hash for the directory>.
Then as I know my laptop isn’t online 24/7, I ssh to my VPS and run
ipfs pin add <hash for the directory> there too so the content is available all the time.
This is where I encounter my biggest disappointment and is where I compare to torrents:
- I add a torrent to my bittorrent daemon (transmission in practice) and it will start downloading (or finding peers or whatever it does in the background) and if there are no seeds available, it will just remember the torrent forever until it can begin, no matter does the network go down or anything that happens.
ipfs pin addcontent, I don’t know anything it is doing, there is just blank until I hopefully see
pinned <hash> recursively, but I am as likely to see something like
Error: Post http://127.0.0.1:5001/api/v0/pin/add?arg=HashProbablyIsIt=json&recursive=true&stream-channels=true: EOF.
I don’t know how to format what my issue is, so I cannot search it, so I hope it’s OK to ask here: are there any issues I could follow or plans to make IPFS seem more like a Bittorrent and instead of silence tell me “started attempting to pin HASH” and keep doing that until it has the content?
It would probably bring other issues like me being unaware of when IPFS has downloaded the content, but maybe there could be another command for that such as
ipfs process hash or
ipfs status hash that could be put into