Follower checks & appeals
Read fresh follower observations and review supported native appeal decisions or ban-reason changes explicitly.
Find it in: Toolkit/Moderation
Check a flagged user's follow date
Enable collection and manual checks
In Message review, turn on Collect new messages for review and Allow manual follower checks. Both checks and collection start off.
Choose Check follower
A matching native author/card is required. Kick's fresh selected-user response can show Following since, an explicit Not following result or Unknown, with observation time. Missing, ambiguous and cached-only data stays Unknown.
Set a minimum follow time
Choose your threshold in Message review. An exact native timestamp can show whether the observed follow duration meets it. A calendar-only date is insufficient for a precise minute comparison.
Cancel or check again
Cancel check stops the read. Checks wait at most five seconds; results expire after one minute and clear on channel/scope/visibility changes, filtering, leaving Moderation or closure.
Review loaded appeals in Kick
Enable Add helpers to Kick's Unban Requests
It starts off in Unban request review.
Open Kick's existing view
Use Chat settings > Mod Actions > Review Unban Requests on a channel where you have access.
Previous / Next and Local context
Navigate already-loaded requests and inspect your existing local note, up to ten filtered buffered messages and eight confirmed current-channel events. Refresh context updates the snapshot.
Review a native decision
Read Kick's appeal reason/chat logs. When fresh request and user identities agree, Review native decision shows the target and Lift ban or Reject choice. Review that plan, then explicitly confirm a second time to invoke the matching native control.
Read the returned result
A matching returned approved/rejected state confirms the appeal result. HTTP success alone or an unsupported result stays Unknown. There is no automatic retry or next-request decision; Kick's native controls remain available.
EnlargeReview an existing ban reason
Open a supported native user card
With appeal helpers enabled, fresh native sanction identity and existing Unban/Untimeout controls can expose Review ban reason. Missing permission, expired data or an unsupported card keeps it unavailable.
Review reason change
Edit the reason and review the target, permanent/timeout type and available remaining duration. Copy or filling a draft does not send anything. Send is explicit and follows Kick's existing native command path.
Understand reapplication
Kick's supported operation reapplies the sanction; it is not an atomic reason edit. Timeout minutes round up and dates can reset. Review these effects before sending. An accepted result without reason confirmation requires reopening the native card to verify it.
Keep access and results clear
Kick owns roles and server results. Only fresh recognized native layouts/identities enable the reviewed action; local context is incomplete. Follower and moderation observations remain in page memory, outside backups. Direct authenticated bulk API jobs are deferred. Actual privileged behavior and server acceptance still need installed acceptance; these candidate guides describe the implemented controls, not completed live testing.
Written for version 1.1. Some controls may be unavailable in an earlier installed release. See release notes.