Log in to an instance in whitelist mode

[dstatyvka]

Steps to reproduce:

1. Go to "Log in" view
2. Type in an URL of instance that is running in whitelist mode

Expected result: "Next" button gets enabled Actual result: "Next" button remains disabled

In all likelihood, GET /api/v1/instance yields 401 Unauthorized, which is misinterpreted by the app. Suggestion: allow user to proceed if the instance check ends up with 401 Unauthorized.

[grishka]

No, the "next" button only works with the list (the existence of which on login is a UX disaster, I figured out this much). You need to use "enter" on the keyboard to log into an instance without choosing it from the list. We'll be making improvements to this screen in future versions.

[dstatyvka]

Unfortunately, it doesn't work this way either.

When I tap the right-arrow on the keyboard (I guess, that's what you meant by "enter"), it says that the server doesn't appear to be a Mastodon instance, and that the method requires an authenticated user.

Sorry for forgetting to mention that.

[grishka]

Hm. It really is weird that /api/v1/instance requires an authenticated user. Had no idea this is possible. I do wonder if authentication also requires an authenticated user 🤪

[dstatyvka]

Yep, it does. According to the docs a user token is required since v3.0.0.

[johncronan]

No, the "next" button only works with the list (the existence of which on login is a UX disaster, I figured out this much). You need to use "enter" on the keyboard to log into an instance without choosing it from the list. We'll be making improvements to this screen in future versions.

Setting up a self-hosted instance (using CapRover) was very easy, but I immediately got hung up on this issue. Glad I found this note!