Skip to content
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

Bad UX on pinning big ipfs-pack trees #633

Closed
nothingismagick opened this issue Mar 29, 2018 · 2 comments
Closed

Bad UX on pinning big ipfs-pack trees #633

nothingismagick opened this issue Mar 29, 2018 · 2 comments

Comments

@nothingismagick
Copy link

I have a pinset (actually a folder with subfolders and lots of files from ipfs-pack) and I want to be able to ipfs-get the whole thing to my computer with ipfs-desktop... Will that work? Would it work with ipfs-cluster?

I also have tried adding the peer ID of the ipfs-pack daemon, but nothing.

I added the Pack Root Hash, but all I see is nothing and a moving yellow bar...

screen shot 2018-03-29 at 17 50 03

I am on OSX 10.12.6 using 0.4.0...

@lidel
Copy link
Member

lidel commented Mar 30, 2018

Pinning huge data set started, but it probably takes time and the only visual feedback that something is happening is yellow spinner. Ouch. This is an important data point, thank you for reporting.

Ideally, app should detect that data fetch takes longer than a few seconds and display some kind of progress bar and ETA (like in torrent client or other download manager).

Good news is that we are designing better UI abstractions for Pinning/Adding in GUI apps that will address these problems.

Check relevant discussions:

@lidel lidel changed the title Usage with ipfs-pack / ipfs-cluster Bad UX on pinning big ipfs-pack trees Mar 30, 2018
@hacdias hacdias closed this as completed Nov 14, 2018
@hacdias
Copy link
Member

hacdias commented Nov 14, 2018

Closing as unrelated to the newer version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants