LotusGuild/cinny
3
0
Fork 0
Code Issues 73 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Status auto-clear only works on the device that set it, and only while that device is open #300

New Issue
Open
opened 2026-10-04 21:09:04 -04:00 by jared · 1 comment
jared commented 2026-10-04 21:09:04 -04:00
Owner
Copy Link
Copy Source

Settings → Account → Status Message → Auto-clear after (for example 1 hour) stores the expiry in localStorage on that device (lotus-status-expiry-<user>). StatusExpiryMonitor (src/app/pages/client/ClientNonUIFeatures.tsx) clears the server status only while that tab or app is running.

So "🍔 Lunch, clear after 1 hour" set on a laptop that is then closed stays on the server (presence.status_msg) until that laptop opens Lotus again, which could be days. The user's other devices actively adopt the server status (resolveStatus in usePresenceUpdater) and never clear it, because they don't know the expiry.

Fix: store the expiry with the status where every device sees it, either Lotus account data (io.lotus.status_expiry) or a field in the synced settings, and let any running device perform the clear. The status-presets work (d0614710) is the natural place.

Related: #283 (DND overwrites the status).

Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny 30e2dbcd, cinny-desktop 8f67ec7, element-call 3b0050e8.

Settings → Account → Status Message → **Auto-clear after** (for example 1 hour) stores the expiry in **localStorage on that device** (`lotus-status-expiry-<user>`). `StatusExpiryMonitor` (src/app/pages/client/ClientNonUIFeatures.tsx) clears the server status only while that tab or app is running. So "🍔 Lunch, clear after 1 hour" set on a laptop that is then closed stays on the server (`presence.status_msg`) **until that laptop opens Lotus again**, which could be days. The user's other devices actively adopt the server status (`resolveStatus` in `usePresenceUpdater`) and never clear it, because they don't know the expiry. **Fix:** store the expiry with the status where every device sees it, either Lotus account data (`io.lotus.status_expiry`) or a field in the synced settings, and let any running device perform the clear. The status-presets work (d0614710) is the natural place. Related: #283 (DND overwrites the status). --- _Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny `30e2dbcd`, cinny-desktop `8f67ec7`, element-call `3b0050e8`._
jared added the bugpriority: lowarea: settings labels 2026-10-04 21:09:04 -04:00
jared commented 2026-10-06 13:01:57 -04:00
Author
Owner
Copy Link
Copy Source

Related (#339): a large share of the "status vanished" reports may not be the expiry. Closing or reloading any Lotus tab sends PUT presence {"presence":"offline"} with no status_msg (usePresenceUpdater.ts handlePageHide), and Synapse clears the status on that write (verified directly). So closing the setting device usually wipes the status at once, before the timer matters. This issue becomes the visible behaviour once that's fixed.

Related (#339): a large share of the "status vanished" reports may not be the expiry. Closing or reloading *any* Lotus tab sends `PUT presence {"presence":"offline"}` with no `status_msg` (`usePresenceUpdater.ts` `handlePageHide`), and Synapse clears the status on that write (verified directly). So closing the setting device usually wipes the status at once, before the timer matters. This issue becomes the visible behaviour once that's fixed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
a11y
Accessibility: keyboard, screen reader, contrast, motion
 area: appearance
Client area: appearance
 area: auth-session
Client area: auth-session
 area: build-ci
Client area: build-ci
 area: calls
Client area: calls
 area: desktop
Client area: desktop
 area: media
Client area: media
 area: messaging
Client area: messaging
 area: mobile
Client area: mobile
 area: moderation
Client area: moderation
 area: navigation
Client area: navigation
 area: notifications
Client area: notifications
 area: settings
Client area: settings
 area: threads
Client area: threads
 bug
Something is not working
 dependencies
Third-party package versions and advisories
 docs
README / LOTUS_* docs wrong or missing
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 needs-human-review
performance
Re-render storms, leaks, heavy work on hot paths
 planning
priority: critical
Data loss, security hole, or crash on a main path
 priority: high
Broken feature or serious usability problem
 priority: low
Minor issue or polish
 priority: medium
Wrong behaviour in an edge case or notable degradation
 qa
Manual QA: shipped, needs a human in a real environment
 question
More information is needed
 research
security
XSS, unsafe URLs, data leaks, auth/session
 tech-debt
Code health, dead code, fragile patterns
 ux
Usability or visual inconsistency
 wontfix
This won't be fixed
No labels area: settings bug priority: low
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
cole (Cole Keller) jared (Jared Vititoe) nathan (Nathan Vititoe)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#300