Map the typing answer's slowmode cooldown to ApiResult::TypingCooldown #307

Open
opened 2026-11-12 14:50:12 +00:00 by charles · 0 comments
Owner

Follow-up of Text chat 11 (#261).

fluxer-core now has ApiResult::TypingCooldown { channel_id, message_send_cooldown_ms }: the composer starts the slowmode countdown from it (spec §3.2 "cooldown from the typing answer"). Nothing produces it yet:

  • fluxer-api typing() uses execute_empty and drops the 200 body {message_send_cooldown_ms, thread_create_cooldown_ms} the server sends under slowmode (spec §3.1).
  • apps/fluxer maps ApiRequest::Typing to ApiResult::TypingOk only.

To do (Text chat 21 or its own small task): read the 200 body and answer TypingCooldown when it has a non-zero message_send_cooldown_ms, TypingOk otherwise. Until then the countdown starts only from the user's own send in a slowmode channel (rate_limit_per_user).

Follow-up of Text chat 11 (#261). `fluxer-core` now has `ApiResult::TypingCooldown { channel_id, message_send_cooldown_ms }`: the composer starts the slowmode countdown from it (spec §3.2 "cooldown from the typing answer"). Nothing produces it yet: - `fluxer-api` `typing()` uses `execute_empty` and drops the 200 body `{message_send_cooldown_ms, thread_create_cooldown_ms}` the server sends under slowmode (spec §3.1). - `apps/fluxer` maps `ApiRequest::Typing` to `ApiResult::TypingOk` only. To do (Text chat 21 or its own small task): read the 200 body and answer `TypingCooldown` when it has a non-zero `message_send_cooldown_ms`, `TypingOk` otherwise. Until then the countdown starts only from the user's own send in a slowmode channel (`rate_limit_per_user`).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#307
No description provided.