[markmnl]

Client API for FMSG-006 Indicators.

• POST /fmsg/:id/indicate {emoji, ttl}:
  • A participant of a sent, non-terminal message shows or clears a short-lived single-emoji state on it, such as ✍️ composing a reply.
  • Answers 202 Accepted with no body.
  • The emoji is validated as for reactions. ttl defaults to 6 and is clamped to 120. An empty emoji or ttl 0 clears.
  • More than one per second per identity and message is accepted but dropped. Clears always go through.
  • Errors: 400, 403, 404 and 409, like react.
• Nothing stored: the indicator is published on NOTIFY indicator as {id, from, emoji, ttl}.
• The hub LISTENs on it on every instance. It sends an indicator WebSocket event {id, root_id, from, emoji, ttl} to the message's other connected participants, with no Web Push.
• The host can LISTEN on the same channel to send the indicator to other hosts over UDP, and NOTIFY it for indicators it receives (fmsgd PR to follow). So the channel works in both directions with one payload shape.
• OAuth: delegated tokens need the write scope.
• README: the route section, a routes-table row and the WS event.

Tests:

• hub routing: delivers to participants, skips the sender and outsiders, adds the root id, drops malformed payloads;
• the throttle;
• integration against Postgres 17:
  • NOTIFY payloads for set, clear and clamp, and the throttle;
  • 400, 403, 404 and 409;
  • nothing stored;
  • the audience and root.

go test ./... passes.

🤖 Generated with Claude Code