Re:Introducing Cloudflare’s IPFS Gateway
by wongarsu on Monday September 17, 2018 @02:16PM
(#18008450)
Now we just need a browser extension that does all that.
If pinning was a button press away it would be much more attractive than making a dns query, resolve the result and pinning that.
Re:Introducing Cloudflare’s IPFS Gateway
by diggan on Monday September 17, 2018 @02:22PM
(#18008504)
Indeed, that's a good idea! I took the freedom to open a issue about this idea on the repository for the IPFS-Companion extension here: https://github.com/ipfs-shipyard/ipfs-companion/issues/581
Re:Introducing Cloudflare’s IPFS Gateway
by aw3c2 on Wednesday September 19, 2018 @01:23PM
(#18025874)
So I've been trying to get "ipfs pin add --progress /ipfs/zdj7WZpLoZYr4AoDUdpCNBVHLi1S8y6muFoCgwUa9kmxUpYCr" to complete but it just takes hours and hours. Is this normal? What might be the issue?
Re:Introducing Cloudflare’s IPFS Gateway
by diggan on Wednesday September 19, 2018 @02:51PM
(#18026700)
Does it get stuck or are you still seeing that blocks are being fetched? If it's still increasing, it's just very large. You can check the download rate by doing `ipfs stats bw --poll`.
Weird thing is, I'm not seeing anyone providing it but I can still pin it. Currently on `Fetched/Processed 1661 nodes` but I'll leave it running and see if it finishes.
But doing `ipfs dht findprovs zdj7WZpLoZYr4AoDUdpCNBVHLi1S8y6muFoCgwUa9kmxUpYCr` should list everyone who is providing it, but I'm getting no responses, which is weird.
Edit: Hm, got stuck at 2007 blocks, are you seeing the same thing?
Edit: Actually found a work-around.
Loading up the hash via our IPLD Explorer reveals the (re-)name of the directory, which happens to be `05ham` and we can call `resolve` on that: "ipfs resolve /ipfs/QmVsEiBRsdiHMvmDVJTNtrXNqSKYdtoepcoZxUrQ8rU7qR/05ham"
Then we get the `/ipfs/zdj7WZpLoZYr4AoDUdpCNBVHLi1S8y6muFoCgwUa9kmxUpYCr` hash which you can use for pinning.