Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #164 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Submit a merge request that closes this issue to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide, and Local Development & SSO to run the app locally (cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.

Description

Current remaining scope, reviewed 2026-10-18: Read-only dormant reporting already exists. Remaining work is the optional scheduler: choose threshold, exemptions, warning, dry-run/confirmation, audit and rollback first. Implement no automatic removals until that policy is recorded. Activity comes from persistent authoritative bot data, with a positive roster control; a failed read must not be interpreted as inactivity.

Verification for this remaining scope

  • Inventory the cited commands/schedulers on current main and link the original implementation and any recorded award before claiming new work.
  • Use real local handlers/SQL/protocol paths with synthetic identities; baseline failures by name. A mock-only success or a healthy process is not live proof.
  • Update both command documentation surfaces when behavior changes. Record updated / pre-release verified / released / live verified separately.
  • This issue does not re-award already accepted behavior. Ask the maintainer to settle original contribution attribution before accepting a follow-up MR.

Entry point: selfhost/messaging-apps/simplex/docs/parity-roadmap-progress.md plus the current command registration and native source. Follow AGENTS.md and the bot rules.

Earlier scope (historical; current qualification above takes precedence)

Context

Signal tracks inactivity tiers and auto-removes 90+-day-silent members hourly. SimpleX has neither.

Acceptance criteria

  • [ ] !dormant (admin) shows activity-tier summary; !dormant <days> lists N+-day-inactive members; !dormant lurkers lists zero-engagement.
  • [ ] A new scheduler auto-removes members past a configurable threshold and logs each removal.
  • [ ] Registered in index.ts and stopped on shutdown; no-ops if disabled.

Technical hints

  • Signal reference: commands/admin/dormant-members.command.ts + scheduler/dormant-removal-scheduler.ts.
  • SimpleX target: commands/admin/dormant.command.ts + scheduler/dormant-removal-scheduler.ts.
  • Derive activity from the bot's own bot_command_usage / simplex_messages (Postgres, persistent) — the SimpleX chat DB is ephemeral and resets on restart.

--- Submit a merge request that says Closes #<this issue iid> in the description. On merge to main, the GitLab webhook auto-awards feature_bounty_<tier> + the standard merge_pr (40 pts) to your scoreboard account. Your commit email must match your Authentik email. Backlog context: docs/simplex-parity-bounties.md.

<!-- bounty-reconciled:2026-10 -->

Relevant files

No relevant files linked yet.

Hints

No hints yet.

Activity

No points have been awarded for this bounty yet.

Comments

No comments yet. Be the first to weigh in.

↑ Top