Bug 479917

Summary: Notifications dialog fetches unread messages from rooms with unfetched content too slowly
Product: [Applications] NeoChat Reporter: Nate Graham <nate>
Component: GeneralAssignee: Tobias Fella <fella>
Status: RESOLVED NOT A BUG    
Severity: minor CC: carl
Priority: NOR Keywords: usability
Version First Reported In: git master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nate Graham 2024-01-16 20:35:55 UTC 
Today's git master on Plasma 6 Wayland on top of Fedora KDE.


STEPS TO REPRODUCE
1. Join a lot of rooms
2. Turn off NeoChat
3. Wait for many messages to accumulate in them, and for at least one message to mention you--e.g. by having NeoChat closed during EU work hours
4. Open NeoChat
5. Open Notifications dialog


OBSERVED RESULT
The Notifications dialog shows me messages only from rooms that have been refreshed recently--i.e. those rooms where I'm likely to already have read the messages. For rooms that I didn't open between steps 4 and 5, the rooms themselves will show a green badge to indicate that there are unread notifications, but the Notifications dialog doesn't show them.


EXPECTED RESULT
The Notifications dialog shows messages mentioning me in all rooms, not just the ones I opened and therefore refreshed recently.
Comment 1 Nate Graham 2024-01-16 20:37:35 UTC 
While I submitted this bug report, the view eventually populated. It was so slow that I thought it wasn't working.

Maybe we can make the bug report about that?
Comment 2 Tobias Fella 2024-07-28 12:56:36 UTC 
The notifications view uses entirely different API than the normal room loading; if there are problems there that cause problems loading some rooms, that has to be a bug in the matrix server software. as for the speed - yeah, things aren't as fast as I'd like them to be, but that's also a problem in the server. We could do a better job in showing that notifications are loading, the main problem there seems to be the same as https://bugs.kde.org/show_bug.cgi?id=490407