If the IS isn't available, the message says you can register but you can't (the `register` button is disabled)

[lampholder]

[lampholder]

Also if the IS comes back online whilst you're on this page of registration, nothing detects that it's come back so you're stuck at this stage.

[turt2live]

Also if the IS comes back online whilst you're on this page of registration, nothing detects that it's come back so you're stuck at this stage.

Expectation is that you can click the register button, and it re-checks the IS being alive. That's conditional on the bug where you can't click the button.

[lampholder]

This replaces the existing behaviour, which when you try and register without the client's being able to access the identity server, you get this:

[lampholder]

Presumably, if your client can't reach the identity server at registration time:

• you could register with just a mxid
• you can't register with an email address (because this relies on the IS being contactable by the client)

The simplest change might be to disable registration when vector.im identity server is down, but I really don't like this since it would break registration even for users who weren't registering with an email address, on matrix.org and on other homeservers which also use the vector.im identity server (which is lots of them).

[turt2live]

@lampholder to reiterate: the expected behaviour is that you can click the button. If you enter an email address despite the warning, the code should give you a friendly error saying "lolnope". Basically: it should work, and we should have the same error handling on clicking the button regardless of liveliness checks because it's possible the IS died or hates your email in the middle of your attempt.

[lampholder]

Oh, okay - cool, thanks.