-
Notifications
You must be signed in to change notification settings - Fork 16
Element is not a functioning messaging application at low live session counts #1894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also invoking #1868, element-hq/element-web#14323, element-hq/element-web#13388 |
#310 is also related. But I think you have stated the issue succinctly and I quite agree. The way people expect a messaging app to work is that when you log in with your username and password you have access to every message ever sent to that username, period. Element does not conform to that expectation (and neither does Matrix as a whole, since as far as I can tell no other client even handles encryption as well as Element does, let alone as well as Element should). |
This seems mostly to be a rant. I appreciate you're frustrated, but walls of text like this don't really help anyone.
That's not what you get from plenty of other messaging applications, including WhatsApp and Signal, to name but two, so I'm not sure it is the way people "expect" a messaging app to work. Anyway, dehydrated devices (#922) should fix the problems reported by the OP. Closing as a duplicate of that. |
@richvdh, I have a distinct example of that being untrue:
There are a great many people used to Discord and Messenger who have never even considered that their messages wouldn't be stored on a server with the decryption key tied to their account.
This should be invalid/not planned, or marked as a duplicate of |
Uh oh!
There was an error while loading. Please reload this page.
Encrypted messages cannot be received (decrypted) when the number of living sessions is zero.
What I expect from a messaging application:
I log in and read messages sent to me.
I log out and go do things.
I log back in and read the messages sent to me while I was away.
Element does not actualize this basic functionality.
When I log out, meaning when I kill the final living session, messages sent to me are never able to be decrypted. I log in and verify using security phrase, but the messages sent while the number of living sessions was zero are lost forever. Those messages have a link to request keys from other sessions. But there are no other sessions.
The same effect is true when zombie sessions exist. When a user closes Element but does not sign out, the session lives on but becomes inaccessible, creating a zombie session. Restoring using security phrase does not decrypt the messages. Those messages have a link to request keys from other sessions. But the other sessions are all permanently lost. Whether invoking the security phrase fails because a decryption action simply isn't triggered or whether the relevant keys are not in the backup I cannot say.
To reproduce 1):
To reproduce 2), which is likely a variation on 1):
This occurs on the web client on at least chrome 90 and firefox 89, archlinux.
app.element.io
This may be what element-hq/element-web#16184 refers to.
The text was updated successfully, but these errors were encountered: