Michael Telatynski
Michael Telatynski
I don't see a Matrix API specific for MSISDN input. Only one for MSISDN+Email. So the client has no way of knowing it is disabled without you trying with a...
This sounds like a server issue, we just call the `/upgrade` endpoint and the HS is responsible for sending the tombstone.
Would need Synapse logs to investigate. Looks like the request timed out after 10 seconds presumably due to no keepalive from Synapse
Agreed, but that timeout isn't client side. ``` 2024-07-29T14:23:58.641Z D FetchHttpApi:
Asking for product input regarding this change landing due to how it misaligns with current stable Element mobile apps which use `sessions`. This likely breaks the Legacy login QR instructions...
> if a user is signed into both Element Web and Element Desktop Or multiple Element Webs, or multiple Element Desktops, or either of the aforementioned + Element X on...
> With QR code sign in, for example, they need to use another device, not just another "session" Not necessarily true. Element X on macOS could be used to scan...
> ...how? Even if the desktop camera could detect the code, there's no way to actually point it at the screen it's connected to. Right? Unless the use has an...
This is a MAS-Synapse special which should have been MSC'd but looks like it missed the boat https://github.com/element-hq/synapse/pull/17509#issuecomment-2298287246
Also supported by matrix-rust-sdk https://matrix-org.github.io/matrix-rust-sdk/src/matrix_sdk/encryption/mod.rs.html#363-378