Prevent spam actions against trusted users
What does this MR do and why?
The current deployment of the spamcheck service does not return blocking spam verdicts. The model accuracy has reached the point that we are ready to implement blocking. This MR adds guardrails to ensure we do not adversely affect paid users with anti-spam mitigations. If a user is on a paid plan and submits a spammable that is flagged as spam, a spam log will be created but no blocking actions will take place.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Example Spam Issue content
Title: Live streaming!!!
Description: Live sports streaming free here https://livestreams.com- Simulate SaaS in GDK.
- Enable spamcheck for local development
- As a regular user create a spam issue. The attempted spam submission should be challenged by recaptcha or blocked.
- Perform the same action as an ultimate user. The spam submission should not be challenged.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.