-
Notifications
You must be signed in to change notification settings - Fork 336
IPFS-aware error page: improve UX when gateway is offline #806
Copy link
Copy link
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekeffort/hoursEstimated to take one or several hoursEstimated to take one or several hoursexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulgood first issueGood issue for new contributorsGood issue for new contributorshelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/readyReady to be workedReady to be workedtopic/design-contentContent design, writing, information architectureContent design, writing, information architecturetopic/design-front-endFront-end implementation of UX/UI workFront-end implementation of UX/UI worktopic/design-uxUX strategy, research, not solely visual designUX strategy, research, not solely visual design
Milestone
Description
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekeffort/hoursEstimated to take one or several hoursEstimated to take one or several hoursexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulgood first issueGood issue for new contributorsGood issue for new contributorshelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/readyReady to be workedReady to be workedtopic/design-contentContent design, writing, information architectureContent design, writing, information architecturetopic/design-front-endFront-end implementation of UX/UI workFront-end implementation of UX/UI worktopic/design-uxUX strategy, research, not solely visual designUX strategy, research, not solely visual design
Type
Fields
Give feedbackNo fields configured for issues without a type.
Recovery from dead public gateways was introduced in #640.
What about scenarios when local gateway goes offline?
Current UX: error page provided by the browser
Right now, opening http://docs.ipfs.io.ipns.localhost:8080 when node is offline ends up with a generic error:
I believe we could improve UX of errors like this.
Improvement: custom error page aware of IPFS options
We should introduce a custom error page tho, to improve UX AND to give user a final say if they choose to start local node and retry, load from original server (if DNSLink), or a public gateway instead.
Custom error page could be used in all recovery contexts (when local node is offline, but also when remote server is down, but has DNSLink).