setKickChatMode (nobilis/src/rpc/methods.rs:3011) works — it drives PUT /api/v2/channels/{slug}/chatroom for followers-only, subscribers-only and slow
mode — and has no caller. Verified: zero references anywhere in src/.
The daemon already reads these settings and reports them: ChatroomUpdatedEvent is
handled at backend/kick/chat.rs:260 and updates followers/subscribers/slow mode. So
moho can tell you the chat is in subscribers-only mode and cannot put it there.
What is needed
Entries wherever a Kick channel is acted on, gated the way the other moderation
actions already are.
Found by the 2026-09-10 coverage review.
`setKickChatMode` (`nobilis/src/rpc/methods.rs:3011`) works — it drives
`PUT /api/v2/channels/{slug}/chatroom` for followers-only, subscribers-only and slow
mode — and has no caller. Verified: zero references anywhere in `src/`.
The daemon already *reads* these settings and reports them: `ChatroomUpdatedEvent` is
handled at `backend/kick/chat.rs:260` and updates followers/subscribers/slow mode. So
moho can tell you the chat is in subscribers-only mode and cannot put it there.
**What is needed**
- Entries wherever a Kick channel is acted on, gated the way the other moderation
actions already are.
Found by the 2026-09-10 coverage review.
Closing as out of scope, on the owner's call: setting a channel's chat mode is a broadcaster setting and belongs on Kick's own site, beside the rest of the settings it sits with.
The distinction worth keeping straight is that reading the mode is a different question and is already answered — ChatroomUpdatedEvent keeps followers-only, subscribers-only and slow mode current (backend/kick/chat.rs), which is how moho can say why a message will not send. It is only setting them that has no caller.
setKickChatMode is kept rather than deleted: it works, and the decision is about scope rather than about the code.
The reason is now recorded at the method itself in 61bcc34. Without that, the next coverage sweep finds the same unreachable capability and files the same ticket again — which is exactly the churn the stale-comment pass (#168) existed to stop.
Closing as out of scope, on the owner's call: setting a channel's chat mode is a broadcaster setting and belongs on Kick's own site, beside the rest of the settings it sits with.
The distinction worth keeping straight is that **reading** the mode is a different question and is already answered — `ChatroomUpdatedEvent` keeps followers-only, subscribers-only and slow mode current (`backend/kick/chat.rs`), which is how moho can say why a message will not send. It is only setting them that has no caller.
`setKickChatMode` is **kept rather than deleted**: it works, and the decision is about scope rather than about the code.
The reason is now recorded at the method itself in [61bcc34](https://git.salastil.com/Salastil/nobilis/commit/61bcc34). Without that, the next coverage sweep finds the same unreachable capability and files the same ticket again — which is exactly the churn the stale-comment pass (#168) existed to stop.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
setKickChatMode(nobilis/src/rpc/methods.rs:3011) works — it drivesPUT /api/v2/channels/{slug}/chatroomfor followers-only, subscribers-only and slowmode — and has no caller. Verified: zero references anywhere in
src/.The daemon already reads these settings and reports them:
ChatroomUpdatedEventishandled at
backend/kick/chat.rs:260and updates followers/subscribers/slow mode. Somoho can tell you the chat is in subscribers-only mode and cannot put it there.
What is needed
actions already are.
Found by the 2026-09-10 coverage review.
Closing as out of scope, on the owner's call: setting a channel's chat mode is a broadcaster setting and belongs on Kick's own site, beside the rest of the settings it sits with.
The distinction worth keeping straight is that reading the mode is a different question and is already answered —
ChatroomUpdatedEventkeeps followers-only, subscribers-only and slow mode current (backend/kick/chat.rs), which is how moho can say why a message will not send. It is only setting them that has no caller.setKickChatModeis kept rather than deleted: it works, and the decision is about scope rather than about the code.The reason is now recorded at the method itself in 61bcc34. Without that, the next coverage sweep finds the same unreachable capability and files the same ticket again — which is exactly the churn the stale-comment pass (#168) existed to stop.