Skip to content

FMSG-003 v0.4.0: indicators client API (FMSG-006) - #43

Merged
markmnl merged 1 commit into
mainfrom
fmsg-003-indicators
Oct 31, 2026
Merged

markmnl merged 1 commit into
mainfrom
fmsg-003-indicators

Conversation

@markmnl

@markmnl markmnl commented Oct 31, 2026

Copy link
Copy Markdown
Owner

Adds the client API that FMSG-006 left to a future FMSG-003 revision. It is optional as a group (route and event together):

  • POST /fmsg/:id/indicate {emoji, ttl}:
    • Only participants may use it, and the message must be sent and not terminal (409 otherwise).
    • The emoji is validated as for react. An empty emoji or ttl 0 clears. ttl defaults to 6 and is clamped to INDICATOR_TTL_MAX.
    • It answers 202 with no body. Nothing is stored.
    • The server delivers it to connected participants and, when it is also the participant's host, sends it on per FMSG-006.
    • The server may drop more than one per second per identity and message, but never clears.
    • Clients should let users turn off composing indicators, and must not send 👀 unless the user opted in.
  • indicator WebSocket event: {id, root_id, from, emoji, ttl}. No Web Push or other durable notification.
  • Other changes: scope, references, route summary and revision table updated. FMSG-006 now points here.

Implemented in markmnl/fmsg-webapi#64.

🤖 Generated with Claude Code

POST /fmsg/:id/indicate {emoji, ttl} shows or clears the caller's
indicator on a message (202, nothing stored), and the indicator
WebSocket event {id, root_id, from, emoji, ttl} delivers other
participants' indicators. Optional as a group. FMSG-006 now points to
it instead of a future revision.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@markmnl
markmnl merged commit dc446b6 into main Oct 31, 2026
@markmnl
markmnl deleted the fmsg-003-indicators branch October 31, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant