#167 · Reconcile SimpleX Q&A lifecycle and remaining delivery guarantees
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 #167 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
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: Resolution, clarification, sharing, soft deletion, stored rejection reason and group reminder code already exist. Reconcile prior MRs/awards against current source and verify those paths rather than re-porting them. Document remaining durable reminder delivery across restarts as a separate thin follow-up after source identity and delivery policy are agreed; no assumed DM identity from ephemeral contact IDs.
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
SimpleX has !question/!answer/!questions/!vote. Missing the resolution, clarification, and cross-group verbs — and the scheduler that DMs askers about unsolved questions.
Acceptance criteria
- [ ]
!solve/!unsolve;!accept <hash> <A#>;!reject <hash> <A#> <reason>;!maybe. - [ ]
!clarify <hash> <text>;!inquire/!cq <hash> <q>(request clarification from asker). - [ ]
!shareq <id> [keywords]shares to the bot's known groups;!dropdeletes. - [ ] A scheduler DMs askers about unsolved questions after a configurable delay; registered in
index.ts.
Technical hints
- Signal reference:
handleAcceptAnswer,handleRejectAnswer,handleSolve,handleClarify,handleInquire,handleShareQuestion;scheduler/question-reminder-scheduler.ts. - SimpleX target: extend
commands/utility/{question,answer}.command.ts+scheduler/question-reminder-scheduler.ts. Tables indatabase/001_q_and_a_tables.sql.
--- 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
Sign in to join the discussion.
No comments yet. Be the first to weigh in.