Marcin Rataj

@rafaelramalho19 raised the problem of having two types of "not found" errors: 1. opening `/files/not/in/mfs` or `/ipfs//nope` (a path that does not exist in parent directory) 2. opening `/invalid-route` that...

If breadcrumbs can't be reused easily, then I'd go with Jessica's sugegstion from the comment above and remove files-specific UI.

@wuniversales this is unrelated, but you should use `ipfs-404.html` for IPFS gateway to pick it up as your 404 page, as noted in [release notes](https://blog.ipfs.io/2020-06-26-go-ipfs-0-6-0/#%F0%9F%9A%AB-custom-404-pages)

:+1: reusing flow already present in other parts of our ecosystem is a good idea.

Quick feedback after playing with stage 1 (https://github.com/ipfs-shipyard/ipfs-webui/pull/1685) implementation: - I believe we should pin each selected item separately Rationale: the way we will do remote pin status check is...

I think both are :+1: thank you, @juliaxbow! - We were avoiding "Upload" in the past (https://github.com/ipfs/ipfs-webui/issues/1951#issuecomment-1209834082) but I am not sure if that rationale still holds up. - We...

@hacdias mind resolving conflicts? I think we should review and ship this, so this work is not lost.

Thanks @hacdias! @juliaxbow any suggestions on what could be the best way to indicate "there are remote pins in progress"? Design requirement: we want it to be visually noticeable, so...

For reference: ``` (node:22646) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code....

GO tests seem to be flaky now too :( https://app.circleci.com/pipelines/github/ipfs/ipfs-webui/830/workflows/e38bc1d3-f5e4-4576-acb7-b9c8417b9fb6/jobs/4936 Might be Travis. Try slowing down/bumping timeouts.