Inform user about potential delays before added content is reachable at public gateway

[lidel]

@Gozala noticed UX issue with adding files via IPFS Desktop and trying to open them on the public gateway:

gozala │ lidel: content uploaded through UI doesn’t seems to be picked up by the gateway for some reason
gozala │ lidel: I just updated go-ipfs and things got picked up
gozala │ lidel: It takes 2-3 mins now which is much better

Still, regular user won't wait 2min for a cat picture to load :-)

Is there anything we can do UX-wise to improve this and ensure content loads faster when added via the GUI app?

My initial thought is to run async preload call when:

• A file is added via IPFS Desktop
• "Share" icon is clicked in Web UI (to start preload before user copies link)

[Gozala]

Just to be clear I'm not sure if that's desktop issue or a network I'm on. Unfortunately I need to run now but I'll try to do some testing to see if there's any difference between desktop and plain go-ipfs, I'm inclined to think it's not the desktop issue.

[olizilla]

@lidel i think this ties in with discussion around infra for the share app. ipfs/infra#461 (comment)

We could do more preloading, but I think we need to start with an agreement on what level of service is expected from the gateway nodes. I think we should push ahead with the ipfs-friends style reciprocal co-hosting ideas first.

I think this also highlights the needs for a more detailed diagnostics command that adds info about the peers and network latency that your node is experiencing... something that we could ask users to run that would help us determine where the delay is coming from. The ipfs diag sys command gives us basic info about versions, interfaces addresses and repo size, but it's not enough info to debug this kind if issue. That and metrics from the gateway that we can use to set expectations in the app.

Ultimately this is a UX challenge of p2p that we need to do a lot more around visulasing and informing the peer of what is going on, as we can't guarantee that any p2p interaction will be fast.

[jessicaschilling]

ipfs/ipfs-webui#1206 (Display a progress dialog while adding files) is functionally a different request, but tugs on similar strings mental-model-wise. Tying these issues together via this comment, so we can use whichever one is solved first to inform how we present information on the other one.