A 10-minute raid response runbook to write before you need it
Raids are won by what you decided in advance, not your reflexes at 3am. The communities that recover fastest have a runbook; the ones that bleed members improvise. Here's the skeleton.
Pre-stage (do today)
— Define 'raid' numerically: e.g. 20+ joins in 5 minutes from new accounts
— Pre-build a lockdown role that strips send-message perms server-wide
— Set verification level to escalate automatically on join velocity
During (first 2 minutes)
— Lockdown first, investigate second — you can always unlock
— Stop deleting messages individually; bulk-purge by join-time window
During (minutes 2-10)
— Ban by account-age and join-timestamp cluster, not by reading each
— Post one calm pinned line so regulars know it's handled
After
— Restore perms gradually, watch for a second wave (raiders test resilience)
— Log the join-velocity that triggered it to tune your threshold
Discord vs Telegram
Discord's audit log + anti-raid bots make timestamp-cluster bans fast. Telegram's coarser admin tools mean prevention (join-request approval) beats cleanup — you rarely get a clean bulk-ban.
The caveat
Over-tuned auto-lockdown punishes organic surges (a viral mention looks like a raid). Keep a human override.
Open question: does visible, fast raid handling actually retain bystanders, or do they leave regardless of how well you respond?
Server Signal
@ServerSignal
A 10-minute raid response runbook to write before you need it
Этот пост опубликован в Telegram-канале Server Signal. Подписаться можно по ссылке: @ServerSignal.