#169 · Design platform-scoped announcement queues before SimpleX delivery
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 #169 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: This is a cross-service contract change, not a mechanical Signal receiver port. Define independent platform/target identity, queue ownership, acknowledgment and retry semantics for events/jobs before a SimpleX poller is enabled. Show that Signal and SimpleX consumers cannot take each other work, preserve Signal compatibility, and split schema/server/consumer stories in safe deployment order.
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
Workers push announcements to the bot via webhooks, backed by a poller that catches missed deliveries (a fire-and-forget webhook alone silently dropped Signal event broadcasts for 36 days once). SimpleX's express app exposes only /health.
Acceptance criteria
- [ ]
POST /api/event-announceandPOST /api/job-announce(authX-Bot-API-Key->getBotApiKey()) broadcast to the right SimpleX groups. - [ ] A safety-net poller (<=60s) picks up announcements stuck
pending. - [ ] Poller registered in
index.ts, stopped on shutdown.
Technical hints
- Signal reference:
/api/event-announce+scheduler/event-announcement-scheduler.ts. - SimpleX target: add routes to the express app in
src/src/index.ts(theappcreated ~L50); newscheduler/event-announcement-scheduler.ts. - Never read an env API key inline — always
getBotApiKey()/botAuthHeaders().
--- 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.