-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Important/urgent to-device messages (eg room keys) can get blocked behind big queues of less important ones #1659
Comments
matrix-org/matrix-spec-proposals#3944 is one proposal to partially mitigate this |
Outcome of crypto workshop today: We consider this input for future sync concepts, rather than trying to tackle this issue in the context of the current architecture. Main reason being that UTDs caused by this issue will resolve after some time and aren't permanent therefore. |
Here is a rageshake of a session experiencing late keys https://github.com/element-hq/element-x-android-rageshakes/issues/1377 As we can see, the queue is mostly room key requests.
Given that key requests are disabled by default now should greatly improve the late key problem |
Eg, if you have another client which spams out room key requests, those requests can take quite a long time to be delivered to a client, and during that time no
m.room.encrypted
events holding actual useful content are delivered.The text was updated successfully, but these errors were encountered: