Reproduction steps
(best guess, not confirmed)
- Open Fluxer on web or desktop.
- Don't open community A at all during this session.
- Wait until community A shows an unread in the community list.
- Click community A. It opens to the channel that has the unread.
Expected behaviour
The channel shows the new message and the unread clears.
Actual behaviour
The unread stays stuck and the new message isn't shown. Refreshing the client shows the message and clears the unread.
Build information
Canary Desktop 2026.1009.45608, Web 2026.1011.165018, macOS 27.0.1 (arm64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-GB
Platform
macOS, Windows, Linux, Web