Inviting a user on a non-existent domain blocks for ages (indefinitely?) (SYN-511)

[matrixbot]

(Imported from https://matrix.org/jira/browse/SYN-511)

(Reported by @ara4n)

[matrixbot]

Jira watchers: @erikjohnston @kegsay @ara4n

[matrixbot]

The JS SDK just calls straight through to the HTTP API. Synapse will try the domain for a while then give up. When testing just now, it was about 30s before coming up with an Internal Server Error. Either way, this is not blocking forever and this is not the JS SDK's role to fix this.

-- @kegsay

[matrixbot]

Rather than won't fixing we should make this a spec or synapse bug then, as it's still a major bad UX bug(!!)

-- @ara4n

[matrixbot]

30 seconds seems reasonable though?

-- @kegsay

[matrixbot]

It's terrible UX if the user mistypes an mxid and then sits there staring at a spinner for 30s. If Synapse gets an early failure (i.e. a 500 or 404 or connection refused) from the target homeserver, it should fail immediately rather than block and timeout.

-- @ara4n

[matrixbot]

What timeouts would people like on this? Do we want a different timeout if we know the domain has a HS?

-- @erikjohnston

[richvdh]

I think this was duplicated by #2047. Closing in favour of that since it has more info.