Repository navigation
Conversation
Remove hidden form fields, load-time tracking, serializer heuristics, and the timing threshold. Keep manual moderation and existing spam records intact. Remove obsolete heuristic tests and exercise public spam filtering through manual moderation. Automatic detection is disabled until the replacement detector is introduced separately.
Contributor
Author
|
supersedes #772 |
sgfost
force-pushed
the
feat/spam-detection-final-final
branch
from
October 27, 2026 23:24
927158a to
184193c
Compare
This branch has not been deployed
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 spam detection that runs on every newly created codebase, event, job, and on every update for member profiles (huey tasks). You can configure a primary model provider and fallback, currently a choice between ASU Voyager (free) and cloudflare (generous free daily usage) served models. The intended/default setup here is to use
Gemma 4 instructfrom voyager and if it fails or takes too long, fall back toclef-omnifrom cloudflare. Though it can easily be configured to only use one or the other and simply wait/retry.Since these perform so well,
SpamModerationno longer primarily acts as a review queue, though we still track when a moderator manually marks something and will not overwrite these decisions.Flagged content remains hidden from public view and the admin page not only works again but looks a bit nicer (see below)
Also:
Note
Deployment: Spam detection defaults to off. Enable and configure it in Wagtail → Settings → Spam detection, and ensure the provider API credentials are deployed.
===