All stats (message counts, reactions, media breakdown, activity heatmap, oldest/newest timestamps) are computed once in a useMemo keyed only on [room]. Since room (the Room object reference) doesn't change for the lifetime of the panel, the stats never update even if new messages/reactions arrive while the Insights panel is open — the panel's numbers are a snapshot from the moment it was opened, with no indication to the user that the data is frozen (there's no "processing..." vs. "processed as of ..." distinction beyond the generic "Based on N locally cached messages" banner).
How to trigger
Open Room Insights, then have someone post several messages/reactions in the room while the panel stays open — the counts don't change.
Suggested fix
Either add a lightweight re-computation trigger on new Room.timeline events (throttled), or explicitly label the snapshot with a timestamp/"Refresh" button so the staleness is intentional and visible rather than silent.
Filed from the September 2026 client audit (branch lotus @ 4bea4895).
**Severity:** low · **Type:** ux · **Confidence:** high
**Location:** `src/app/features/room-settings/RoomInsights.tsx:72-140`
### Problem
All stats (message counts, reactions, media breakdown, activity heatmap, oldest/newest timestamps) are computed once in a `useMemo` keyed only on `[room]`. Since `room` (the `Room` object reference) doesn't change for the lifetime of the panel, the stats never update even if new messages/reactions arrive while the Insights panel is open — the panel's numbers are a snapshot from the moment it was opened, with no indication to the user that the data is frozen (there's no "processing..." vs. "processed as of ..." distinction beyond the generic "Based on N locally cached messages" banner).
### How to trigger
Open Room Insights, then have someone post several messages/reactions in the room while the panel stays open — the counts don't change.
### Suggested fix
Either add a lightweight re-computation trigger on new `Room.timeline` events (throttled), or explicitly label the snapshot with a timestamp/"Refresh" button so the staleness is intentional and visible rather than silent.
---
---
_Filed from the September 2026 client audit (branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · Medium & Low milestone 2026-09-12 01:51:32 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: low · Type: ux · Confidence: high
Location:
src/app/features/room-settings/RoomInsights.tsx:72-140Problem
All stats (message counts, reactions, media breakdown, activity heatmap, oldest/newest timestamps) are computed once in a
useMemokeyed only on[room]. Sinceroom(theRoomobject reference) doesn't change for the lifetime of the panel, the stats never update even if new messages/reactions arrive while the Insights panel is open — the panel's numbers are a snapshot from the moment it was opened, with no indication to the user that the data is frozen (there's no "processing..." vs. "processed as of ..." distinction beyond the generic "Based on N locally cached messages" banner).How to trigger
Open Room Insights, then have someone post several messages/reactions in the room while the panel stays open — the counts don't change.
Suggested fix
Either add a lightweight re-computation trigger on new
Room.timelineevents (throttled), or explicitly label the snapshot with a timestamp/"Refresh" button so the staleness is intentional and visible rather than silent.Filed from the September 2026 client audit (branch
lotus@4bea4895).