The pagehide keepalive write sent {"presence":"offline"} with no status_msg. Synapse treats a missing status_msg as clearing it, so closing or reloading any Lotus tab wiped the user's custom status for everyone. It happened intermittently, because the 10 s presence rate limit sometimes rejected the write. It now sends the current status with the offline state.
Verified on the local Synapse, with the status set from another device:
step
before
after
reload 1
status gone
online / Gone fishing
reload 2
—
online / Gone fishing
close tab
status gone
offline / Gone fishing
The close-time body is now {"presence":"offline","status_msg":"Gone fishing"}.
tsc clean · unit tests 1325 pass · ESLint/Prettier clean on the changed file.
Fixes #339.
The `pagehide` keepalive write sent `{"presence":"offline"}` with no `status_msg`. Synapse treats a missing `status_msg` as clearing it, so closing or reloading any Lotus tab wiped the user's custom status for everyone. It happened intermittently, because the 10 s presence rate limit sometimes rejected the write. It now sends the current status with the offline state.
**Verified** on the local Synapse, with the status set from another device:
| step | before | after |
|---|---|---|
| reload 1 | status gone | `online` / Gone fishing |
| reload 2 | — | `online` / Gone fishing |
| close tab | status gone | `offline` / Gone fishing |
The close-time body is now `{"presence":"offline","status_msg":"Gone fishing"}`.
`tsc` clean · unit tests 1325 pass · ESLint/Prettier clean on the changed file.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
The pagehide keepalive write sent { presence: 'offline' } with no
status_msg, which Synapse treats as clearing it, so closing or reloading
any Lotus tab wiped the user's status for everyone (intermittently, as
the 10 s presence rate limit sometimes 429'd the write). It now sends the
current status along with the offline state.
Verified against the local Synapse: with a status set from another
device, two reloads and a tab close keep it (server shows
offline/"Gone fishing" after the close; before, the first reload wiped it).
Fixes#339
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
jared
merged commit fea9484a03 into lotus2026-10-11 22:57:25 -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.
Fixes #339.
The
pagehidekeepalive write sent{"presence":"offline"}with nostatus_msg. Synapse treats a missingstatus_msgas clearing it, so closing or reloading any Lotus tab wiped the user's custom status for everyone. It happened intermittently, because the 10 s presence rate limit sometimes rejected the write. It now sends the current status with the offline state.Verified on the local Synapse, with the status set from another device:
online/ Gone fishingonline/ Gone fishingoffline/ Gone fishingThe close-time body is now
{"presence":"offline","status_msg":"Gone fishing"}.tscclean · unit tests 1325 pass · ESLint/Prettier clean on the changed file.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
The pagehide keepalive write sent { presence: 'offline' } with no status_msg, which Synapse treats as clearing it, so closing or reloading any Lotus tab wiped the user's status for everyone (intermittently, as the 10 s presence rate limit sometimes 429'd the write). It now sends the current status along with the offline state. Verified against the local Synapse: with a status set from another device, two reloads and a tab close keep it (server shows offline/"Gone fishing" after the close; before, the first reload wiped it). Fixes #339 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5