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
A conversation hosted on server "S" adds a user from server "C" as a federated user
Messages are exchanged and the conversation is not the top of the list anymore
A user from server "S" edits a message
Expected behaviour
The conversation should not be moved to the top of the conversation list again (this seems to be the case for non-federated conversations)
Actual behaviour
The conversation is moved to the top again, although it is still marked as read.
Not sure if we need to take into account if it was the last message because of soft-updating, but in the observed case it was not the last message.
Talk app
Talk app version: 19.0.0
The text was updated successfully, but these errors were encountered:
How to use GitHub
Steps to reproduce
Expected behaviour
The conversation should not be moved to the top of the conversation list again (this seems to be the case for non-federated conversations)
Actual behaviour
The conversation is moved to the top again, although it is still marked as read.
Not sure if we need to take into account if it was the last message because of soft-updating, but in the observed case it was not the last message.
Talk app
Talk app version: 19.0.0
The text was updated successfully, but these errors were encountered: