Add anti-raid and anti-nuke protection #19

2026-10-20T21:00:51Z

FernandoJVideira commented

2026-10-20 21:00:51 +00:00

Anti-raid and anti-nuke protection, modelled on Wick. Everything is off until turned on.

Join Gate: account age, no avatar, advertising names, username patterns (plain text, no regex), unverified and unauthorized bots
Raid mode: join-rate detection, invite pausing, kick/ban/timeout of raiders; survives a bot restart
Anti-nuke: per-action limits over a window; offenders are quarantined (roles stripped and saved)
Lockdowns of a channel, the server, or joins
Heat: decaying per-member spam score, panic mode for spam waves, mention-flood lockdown
Snapshots of roles and channels (every 6h, last 3 kept) and a restore that rebuilds what a nuke deleted
Alerts to a channel, plus DMs of critical alerts to the owner and trusted users

Security model: anything that weakens protection (turning off, unlocking, releasing, restoring) needs the owner or a trusted user, checked by the bot/API itself rather than Discord command permissions. Only the owner edits the trusted list. Lookups fail closed. Roles and channels are validated (no @everyone, no dangerous permissions).

Stacked on the tickets branch: merge the tickets PR first.

🤖 Generated with Claude Code

Anti-raid and anti-nuke protection, modelled on Wick. Everything is off until turned on. - Join Gate: account age, no avatar, advertising names, username patterns (plain text, no regex), unverified and unauthorized bots - Raid mode: join-rate detection, invite pausing, kick/ban/timeout of raiders; survives a bot restart - Anti-nuke: per-action limits over a window; offenders are quarantined (roles stripped and saved) - Lockdowns of a channel, the server, or joins - Heat: decaying per-member spam score, panic mode for spam waves, mention-flood lockdown - Snapshots of roles and channels (every 6h, last 3 kept) and a restore that rebuilds what a nuke deleted - Alerts to a channel, plus DMs of critical alerts to the owner and trusted users Security model: anything that weakens protection (turning off, unlocking, releasing, restoring) needs the owner or a trusted user, checked by the bot/API itself rather than Discord command permissions. Only the owner edits the trusted list. Lookups fail closed. Roles and channels are validated (no @everyone, no dangerous permissions). **Stacked on the tickets branch: merge the tickets PR first.** 🤖 Generated with [Claude Code](https://claude.com/claude-code)

FernandoJVideira added 2 commits 2026-10-20 21:00:51 +00:00

Add support tickets that work with private threads d294b3463b

Members open a ticket from a panel in the ticket channel: one button per
category (a dropdown past five), then a short form. Each ticket is a private
thread named after the category, number and opener, with a first message
that mentions the category's staff role so its members join, and Claim and
Close buttons.

- Claim: staff (the category's role, or Manage Threads / Manage Server)
  take a ticket; the first message shows who has it.
- Close: the opener or staff close it, with an optional reason. The thread
  is locked and archived, and the log channel gets a summary and a .txt
  transcript of the whole thread.
- /ticket add|remove|claim|close inside a ticket; /tickets setup,
  /tickets category add|remove|list and /tickets panel for admins.
- Per-member limit on open tickets (default 1), per-server ticket numbers
  handed out atomically, a deleted thread closes its ticket.
- The dashboard asks the bot to post or refresh the panel through
  ticket_commands (LISTEN/NOTIFY, like music); the listener reconnects if
  the database connection drops.
- Setup warns about missing bot permissions in the ticket and log channels.

The flows live in internal/tickets behind small Discord and store
interfaces, with unit tests on fakes; the repo and the listener have
integration tests (-tags integration, TICKETS_TEST_DB).

Needs the ticket tables (velox-dashboard-api migration 000016_tickets).
.gitignore gains the /tldr benchmark rules so private chat exports and
benchmark results on disk can't be committed from this branch.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Add anti-raid and anti-nuke protection 3f87e68a2c

Join Gate (account age, avatar, advertising and username filters, bot
checks), raid detection with invite pausing, anti-nuke quarantine of
admins who mass delete, manual and automatic lockdowns, a decaying heat
score against spam, role and channel snapshots with restore, and alert
DMs to the owner and trusted users. Everything that weakens protection
is limited to the owner and the trusted list.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

FernandoJVideira merged commit e453a9ba94 into dev

2026-10-20 21:04:13 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FernandoJVideira/velox-bot#19