#85 residual: per-sender invite cooldown + idle DM-room TTL leave

robocub commented

2026-07-11 16:51:02 +00:00

Collaborator

Follow-up to the #85 core (shipped alpha.18: audit.jsonl rotation + post-join member-count check). Residuals: (1) a per-sender cooldown on invite acceptance (the global #84 gate bounds total volume, but a single sender can churn within it); (2) leave idle/empty DM rooms after a TTL (a user who DMs then leaves strands an empty room). Both fit the shared periodic mgmt maintenance task in the #83 residual.

robocub referenced this issue

2026-07-11 16:51:31 +00:00

#79 finding 5 (HIGH): unthrottled DM invite auto-join + unrotated audit.jsonl; trust is_direct #85

robocub referenced this issue

2026-07-11 17:50:13 +00:00

#83 residual: reap abandoned-pending link-probe rooms (periodic sweep) #87

robocub commented

2026-07-11 17:50:13 +00:00

Author

Collaborator

Fixed + shipped in v0.3.0-alpha.19 (deployed 2026-07-11). #89a: a per-sender cooldown on invite auto-joins (reuses mgmt_cooldown_secs + a separate stamp map) so a self-serve user can't churn invites. #89b: the maintenance sweep (see #87) leaves DM rooms that have gone empty (only the bot remains), guarded by the same safe-room set. Out of scope: leaving idle-but-occupied rooms (needs activity tracking).

Fixed + shipped in **v0.3.0-alpha.19** (deployed 2026-07-11). #89a: a per-sender cooldown on invite auto-joins (reuses `mgmt_cooldown_secs` + a separate stamp map) so a self-serve user can't churn invites. #89b: the maintenance sweep (see #87) leaves DM rooms that have gone empty (only the bot remains), guarded by the same safe-room set. Out of scope: leaving idle-but-*occupied* rooms (needs activity tracking).

robocub closed this issue

2026-07-11 17:50:13 +00:00

Rows
Columns

#85 residual: per-sender invite cooldown + idle DM-room TTL leave #89