Repository navigation
Add automatic Discord spam moderation - #94
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds automatic moderation matching Fuddy: a 10-minute timeout, a 24-hour timeout, then an automatic ban for qualifying spam incidents. Strikes reset after 30 quiet days; the verified owner is exempt and ordinary GitHub sharing stays allowed.
A server-scoped Durable Object checks new messages once a minute, persists action checkpoints, suppresses burst/retry double-strikes, and sends ambiguous promotions only to a private log. Includes privacy disclosure and operational/recovery documentation. Existing commands and schedules remain intact.
Updates the existing undici override to 7.30.1 to clear the pre-existing audit failure, matching Fud AI.
Validation: 41 Worker tests (24 moderation regressions), 4 fuzz suites, production Next.js build, zero npm audit vulnerabilities, and Wrangler deployment dry run pass. No real member was used for enforcement testing.