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

Opening a conversation via a notification is slow #548

Open
duogenesis opened this issue Jan 7, 2025 · 0 comments
Open

Opening a conversation via a notification is slow #548

duogenesis opened this issue Jan 7, 2025 · 0 comments

Comments

@duogenesis
Copy link
Member

duogenesis commented Jan 7, 2025

When you open a conversation via a notification, connecting to the chat server and refreshing the conversation takes an annoyingly long time. The problem is probably worse for users with big inboxes.

One (part of a solution) might involve more aggressive caching on the client. Though I'd rather use this as a last resort because I don't want to add much complexity to the frontend.

Another solution might be to move away from XMPP. When logging-in via XMPP, a connection needs to be established before subsequent activities happen. This takes a few round trips between the server and client. But it's possible to fetch a conversation in just one round trip by offering the authentication token when requesting the conversation. XMPP doesn't allow this, but a custom protocol can.

Related: duolicious/duolicious-backend#446

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

1 participant