| ▲ | foresto 4 hours ago | |||||||
In this case, it's what you do when signing in from a new device (or browser) to attest that it's yours. It avoids warnings to you and your contacts that a device has gained access to your account without your approval. It involves doing one of these things: - Comparing a short sequence of emoji on each device and confirming that they match. - Using one device to scan a QR code displayed by the other. - Entering a recovery key (a line of text) that you were given when you first set up the account. Pretty quick and easy in most cases, although some clients can be glitchy in this area and require trying again. (Gripe: The recovery key approach was unfortunately made painful and error-prone in recent Element releases, by disabling the option to choose a passphrase instead, but most people can simply use one of the other two approaches.) | ||||||||
| ▲ | SilverElfin an hour ago | parent | next [-] | |||||||
Maybe I’m missing something but why does this service need this process while Discord or whatever don’t? | ||||||||
| ▲ | g-b-r 3 hours ago | parent | prev [-] | |||||||
> Pretty quick and easy in most cases The experiences reported here seem to say otherwise... As others, anyhow, I haven't tried again recently > (Gripe: The recovery key approach was unfortunately made painful and error-prone in recent Element releases, by disabling the option to choose a passphrase instead, but most people can simply use one of the other two approaches.) I last tried Element about six months ago, but for years using the recovery key was either impossible or close to it, and mostly just for idiotic UI mistakes that were never corrected (something like you had to enter the key where they wanted the passphrase or the opposite). To my recollection the version from six months ago worked better in that regard, but it was still asking to enter the passphrase where you actually had to enter the recovery key. | ||||||||
| ||||||||