Desynced read/unread status on @mentions

Summary

I have noticed that the "read" status on messages with @mention for me or my role(s) due to current server instabillity, gets desynced between fluxer server and the clients. You cannot mark it as read, since the desync thinks its already have "read" status, while the client insists its "unread" (red dots everywhere) One soltion i found is to right click the message and set it as unread, then i can mark it as read and the red dot for that message goes away. Perhaps if i mark a message as read, that the server thinks already is marked, sync back to the client so the client can mark it as read.

Steps to reproduce

Get @mentioned some server instabillity-ish read the message ..