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

Reactions take time until seen by others #7064

Open
Tracked by #7232
nickvergessen opened this issue Mar 25, 2022 · 2 comments
Open
Tracked by #7232

Reactions take time until seen by others #7064

nickvergessen opened this issue Mar 25, 2022 · 2 comments

Comments

@nickvergessen
Copy link
Member

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. User A write a message
  2. User B react to the message

Expected behaviour

User A sees the reaction

Actual behaviour

User A sees the reaction only after the 0-30s of the chat polling pass. This is some what a performance optimisation, but it can be totally unexpected in this case. But if otherwise 70 people react 70 people reload the chat 70 times => 4.9k requests...
Might not be solvable for now, but want this to be documented at least

Talk app

Talk app version: master

@SystemKeeper
Copy link
Contributor

Similar to typing indicator we could send a signaling message to the active participants in the room when adding/removing a reaction. Limiting it to external signaling should have no big performance issue and would not increase the load on the NC side

@nickvergessen
Copy link
Member Author

Yeah can also just close it and it comes when all chat messages come via HPB

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

No branches or pull requests

3 participants