Follows can be imported and synced (#56) but not changed: you cannot follow or unfollow a channel from moho, cannot subscribe, and cannot raid another channel when your own stream ends. All three are ordinary buttons on kick.com.
Done looks like: follow/unfollow from the channel header, and an outbound raid for an account that can.
Follows can be imported and synced (#56) but not changed: you cannot follow or unfollow a channel from moho, cannot subscribe, and cannot raid another channel when your own stream ends. All three are ordinary buttons on kick.com.
**Done looks like:** follow/unfollow from the channel header, and an outbound raid for an account that can.
Scope cut to following only, per the owner: subscribing is money and raiding is a broadcaster's own gesture, and neither belongs behind a button in a chat client.
Following is done. The same endpoint both ways — POST to follow, DELETE to stop — which is how kick.com's own button works. It matters more than it looks here: the follow list is what this account's channel list syncs from, so following in moho keeps that list editable from the place it is read. The header carries a heart that fills when this account follows, and the state is absent rather than false for an account that is not signed in, since "not following" and "cannot say" are different answers.
Verified live: reading the state works (tayl31gh → following), and unfollowing works and is reflected back within a second.
One thing testing taught, at a cost. Kick rate-limits follow actions hard — following and unfollowing the same channel twice in a row returns 429 for minutes, not seconds. My unfollow of tayl31gh succeeded and the immediate re-follow did not, so that follow is currently off and retrying every 90s. The error is reported in words now ("try again in a few minutes") rather than as a bare 429, which is the useful half of what that cost.
Scope cut to following only, per the owner: subscribing is money and raiding is a broadcaster's own gesture, and neither belongs behind a button in a chat client.
Following is done. The same endpoint both ways — POST to follow, DELETE to stop — which is how kick.com's own button works. It matters more than it looks here: the follow list is what this account's channel list syncs from, so following in moho keeps that list editable from the place it is read. The header carries a heart that fills when this account follows, and the state is **absent rather than false** for an account that is not signed in, since "not following" and "cannot say" are different answers.
Verified live: reading the state works (`tayl31gh` → following), and unfollowing works and is reflected back within a second.
**One thing testing taught, at a cost.** Kick rate-limits follow actions hard — following and unfollowing the same channel twice in a row returns 429 for *minutes*, not seconds. My unfollow of `tayl31gh` succeeded and the immediate re-follow did not, so that follow is currently off and retrying every 90s. The error is reported in words now ("try again in a few minutes") rather than as a bare 429, which is the useful half of what that cost.
nobilis df660ea, moho https://git.salastil.com/Salastil/moho/commit/5f817d3
Salastil
changed title from Kick: following, subscribing and raiding from the client to Kick: following from the client2026-09-03 21:26:21 -04:00
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.
Follows can be imported and synced (#56) but not changed: you cannot follow or unfollow a channel from moho, cannot subscribe, and cannot raid another channel when your own stream ends. All three are ordinary buttons on kick.com.
Done looks like: follow/unfollow from the channel header, and an outbound raid for an account that can.
Scope cut to following only, per the owner: subscribing is money and raiding is a broadcaster's own gesture, and neither belongs behind a button in a chat client.
Following is done. The same endpoint both ways — POST to follow, DELETE to stop — which is how kick.com's own button works. It matters more than it looks here: the follow list is what this account's channel list syncs from, so following in moho keeps that list editable from the place it is read. The header carries a heart that fills when this account follows, and the state is absent rather than false for an account that is not signed in, since "not following" and "cannot say" are different answers.
Verified live: reading the state works (
tayl31gh→ following), and unfollowing works and is reflected back within a second.One thing testing taught, at a cost. Kick rate-limits follow actions hard — following and unfollowing the same channel twice in a row returns 429 for minutes, not seconds. My unfollow of
tayl31ghsucceeded and the immediate re-follow did not, so that follow is currently off and retrying every 90s. The error is reported in words now ("try again in a few minutes") rather than as a bare 429, which is the useful half of what that cost.nobilis df660ea, moho https://git.salastil.com/Salastil/moho/commit/5f817d3
Kick: following, subscribing and raiding from the clientto Kick: following from the client