Skip to content

Matrix chat: external matrix users are redirected to matrix.to instead of their homeserver's web client

Since synapse#11895 was merged and released (probably somewhere between v1.51 and v1.60), Matrix servers do not respond to the /_matrix/client path anymore. The path was changed to a (from my point of view) unsuitable location, which will prevent many Matrix homeservers from adopting it (see the issue I openend: synapse#14722).

This broke our discovery of the user's Matrix web client for users with external Matrix accounts.

Now users with external Matrix accounts end up below https://matrix.to/ (with the generic web client selection dialog) instead of opening the web client of their Matrix homeserver. This is rather confusing - especially for new users of Matrix.

What should we do now?

  • A) run a quick survey of currently used external Matrix servers in our grouprise instances and provide a default list of mappings between Matrix homeservers and their web clients (e.g. as a configuration)
  • B) instead of redircting to matrix.to we could respond with a helpful message like "now open your matrix client and switch to the room #"
  • C) adjust the Matrix homeserver setups within our reach in order to comply with the new discovery endpoint

Technically (C) would be appropriate, but personally I would not be willing to do that work (at least not before the Matrix people confirmed, that the new way will really stay here for a long time). Thus, from my point of view, (A) would be ugly, but preferable.

What do you think?