#29 · Award `share_event` points when an event is forwarded via Signal bot
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 #29 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
Description
In review — implementation already exists in !300. Coordinate with that MR and its author; do not start a duplicate implementation. This status is source/MR evidence, not a claim that release or live acceptance is complete.
Earlier scope (historical; current qualification above takes precedence)
Context
share_event is in the scoreboard CHECK constraint (5 pts) but no service awards it. Wire event-service to the bot's !share path so members get credit for amplifying events.
Acceptance criteria
- [ ] When Signal bot forwards an event link, it pings event-service
/api/events/<id>/shared - [ ] Event-service awards
share_eventto the sharing user (idempotent persource_id=share:<event_id>:<user_id>) - [ ] Endpoint authenticated with
BOT_API_KEY
Technical hints
- Look at
apps/signal-bot/src/src/integrations/event-client.tsfor existing event API calls - Idempotency idiomatic for scoreboard — already enforced by
idx_point_events_sourceunique index
--- *Submit a merge request that says Closes #<this issue iid> in the description. On merge to main, the GitLab webhook will auto-award your bounty + the standard merge_pr (40 pts) to your scoreboard account. Email on commit must match your Authentik email.*
<!-- bounty-reconciled:2026-10 -->
Relevant files
No relevant files linked yet.
Hints
No hints yet.
Activity
- +50 Hugo Zarate earned S bounty Oct 18
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.