Skip to content
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

[Feature Request] better support for massive lobbies with E2EE enabled #2035

Open
ZeeWanderer opened this issue Oct 25, 2024 · 0 comments
Open

Comments

@ZeeWanderer
Copy link

ZeeWanderer commented Oct 25, 2024

Describe the problem

As it says in the title, recently i joined a server with about 7K users per room at the time of writing and about 8K total and E2EE is enabled. I know most of the issue stems from key exchange latency and serverside delays but you might be able to mitigate it somewhat.

Describe the solution you'd like

Firstly some more chat caching, i get connection lost headers and then only a small portion of the chat is available.
Message ordering is somewhat out of wack, different sessions show different ordering and after relaunching it can jump around, no idea if you even can mitigate that
Other features, like verifying another session (emoji test) seem to be affected too. If it's due to background keys fetch or something similar, verification could be prioritized instead.
Better support for editing messages in those conditions, currently on sending an edit the textbox remains for quite some time, an indicator on the message itself that it's sending would be better. And if possible, re-edit, with cancellation of any uncompleted edit posts.

Also a lot of people immediately start asking about Unable to decrypt message and in this case it can remain for a long time so a tooltip on hover would be nice.

Alternatives considered

No response

Additional context

Other clients i have tried have the same problems, would be nice to have at least one with extended support for massive E2EE in poor performance conditions if at all possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@ZeeWanderer and others