[StavrosK]

Yes, I've reported everything, and they were extremely helpful (to the point where they debugged things with me), but nothing changed.

> Why does it take several days to pin something?

The daemon doesn't act like a torrent client, where you can add a pin and then come back later to check progress. You need to do an HTTP POST (or whatever verb) and then wait until it's done, which due to availability issues and size might take days to complete.

[feanaro]

> Yes, I've reported everything, and they were extremely helpful (to the point where they debugged things with me), but nothing changed.

Do you remember how long ago this was? I'm still hoping this is a solvable problem since I really want IPFS to work.

> The daemon doesn't act like a torrent client, where you can add a pin and then come back later to check progress. You need to do an HTTP POST (or whatever verb) and then wait until it's done, which due to availability issues and size might take days to complete.

Oh. That does sound awful. I wonder why they designed it like that.

[StavrosK]

> Do you remember how long ago this was? I'm still hoping this is a solvable problem since I really want IPFS to work.

This was around two years ago. I hope it'll get solved too, but it doesn't seem to have been solved yet.

> I wonder why they designed it like that.

I guess it was just easier, but they haven't done anything in years. The ticket has been open since 2016: https://github.com/ipfs/go-ipfs/issues/3054

[martindbp]

I recently looked into this, and now there at least seems to be a --progress option to 'pin add' which shows number of "nodes" fetched/processed (IPLD nodes?). Not sure how to put that into greater context though, i.e. how many nodes are there, and how does it translate into bytes? But it's better than nothing.

[StavrosK]

Ah, I'll check to see if that's in the API, although it's not super helpful if I still need to keep the connection open. Still, as you say, better than nothing!