You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ Built for open-source community groups that get flooded with spam-bot join reque
20
20
-**`/ban`** = 封禁 (ban) — **removes** the user; deletes only the replied message; banned for `/bantime` (default permanent, or timed so they can rejoin after).
21
21
-**`/sb`** = 举报并封禁 (report + ban) — like `/ban` but also **deletes all of the user's messages** (spam cleanup).
22
22
-**`/warn`** = strike a user (auto-kick after `warn_limit`, default 3 — counts persist across restarts); **`/clearwarn`** = clear a user's strikes.
23
+
> **Notes:** admin commands must be sent **non-anonymously** — an anonymous-admin post appears as the group itself, not a user, so it can't pass the admin check. And if a user applies to several guarded groups with **different** required channels, the DM follow-prompt covers the first pending group's channel; sharing one required channel across groups gives the smoothest flow.
23
24
-**Configurable ban duration** (`/bantime`, admins): `/bantime 0` = permanent (default), `/bantime 7d` / `12h` / `30m` / `3600` (seconds). Sets the duration used by `/ban`, `/sb` and the verification auto-ban. Seeded from `ban_seconds`; a runtime change resets to the config value on restart.
24
25
-**Verification anti-spam.** A failed verification (wrong answer / timeout) **declines** the request (never an immediate permanent ban) and the applicant must wait `verify_retry_seconds` (default 180) before re-applying; after `verify_max_fails` failures (default 3) **within a few hours** they are **auto-banned** for the configured duration. Strikes persist across restarts, reset on a successful verification, and **age out** (so a genuine user's isolated mistakes don't accumulate). The auto-ban is only cleared if it actually succeeds — where the bot lacks ban rights, strikes are kept and admins keep getting alerted.
0 commit comments