| ▲ | pkulak 3 hours ago | ||||||||||||||||
Despite all the gnashing of teeth in this thread, this seems reasonable. This seems to only prevent you from logging into your account, with only a password, NOT verifying it (by dismissing all the prompts asking you to do so), and then sending (and receiving new!) encrypted messages anyway. I've never used an unverified Matrix account in the 6 years that I've been an active user. Verification used to be a bit finicky, but it's pretty seamless now. And once the QR code login stuff is better supported, it will be dead easy. | |||||||||||||||||
| ▲ | Gigachad 2 hours ago | parent | next [-] | ||||||||||||||||
Doesn’t verification also exchange encryption keys, letting you decrypt messages from before you logged in? I remember that being a huge issue where you would see unable to decrypt messages. Probably just bad UX to let people skip the verification step. | |||||||||||||||||
| |||||||||||||||||
| ▲ | IlikeKitties 3 hours ago | parent | prev [-] | ||||||||||||||||
> Despite all the gnashing of teeth in this thread, this seems reasonable I think it's not the requirement itself that's the crucible of discussion but the issues are rather that the blog post should have explicitly defined what verification is in it's second sentence and that matrix/element still is barely useable even for reasonably technical users. | |||||||||||||||||
| |||||||||||||||||