Simplify UX Around The State Of Gateway Redirect

[lidel]

Based on anecdotal evidence 🙃 less savvy users are often confused about "gateway redirect".
It is mostly my fault. The term is used due to legacy reasons: initial name of this add-on was "ipfs-gateway-redirect".

To make things worse, current GUI always displays local gateway as "HTTP GATEWAY", no matter if it is actually used (enabled via redirect) or not:

Enabled:
Disabled:

Here's an Idea

"HTTP Gateway" should reflect the URL of currently active gateway:

• If redirect is enabled, its value is URL of "Custom Gateway" (eg. http://127.0.0.1:8080)
• If redirect is disabled, its value is URL of "Public Gateway" (eg. https://ipfs.io)

Additionally, we could rename toggle to make it self-explanatory and easier to understand:

• "Enable Gateway Redirect" → "Switch to Custom Gateway"
• "Disable Gateway Redirect" → "Switch to Public Gateway"

If we make these two changes, then we can decrease cognitive load by removing "Redirect" status from UI.

[daviddias]

@lidel I like this proposal 👍

[lidel]

Done!

• This change is in v2.1.1beta4 🌵
• We may be missing translations for two labels. If anyone wants to help with translation, check https://crowdin.com/project/ipfs-companion
• UX note: at some point in future, during general polish, we may consider cheating a bit, and display new HTTP Gateway immediately (instead of waiting for actual switch to propagate, like it happens in demo below).

[olizilla]

I'm all for this! #320 has got too big! I'd included a similar change there, but it's trapped in a larger changeset.

I love how similar these changes have turned out. Feels like we're heading in the same direction!