You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
User A write a message
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
The text was updated successfully, but these errors were encountered:
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
How to use GitHub
Steps to reproduce
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
The text was updated successfully, but these errors were encountered: