#170 · SimpleX Redis-backed rate-limiting + cache (AI throttle parity)
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 #170 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
Description
Context
A Redis container is provisioned for the SimpleX bot but unused. Signal rate-limits AI (e.g., 20/hour/user) and caches via Redis.
Acceptance criteria
- [ ] Redis client initialized at startup; AI commands enforce a per-user rate limit.
- [ ] At least one hot path (wiki/embeddings or group list) cached with a sensible TTL.
- [ ] Graceful no-op if Redis is unreachable (don't crash the bot).
Technical hints
- Reuse
redis-client.ts/ rate-limit helpers in shared-utils. - SimpleX target: init in
src/src/index.ts; apply in the relevant command files.
--- 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.
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.