[ SmokeDetector | MS ] Mostly non-latin body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, blacklisted user (153): jnvu-results-2022 by scrylearning on meta.SE (@Ollie)
@Luuklag No, the error responses MS received are typical of the CloudFront rate limiting SE uses on the SE API, which is only one of the types of rate limiting SE uses for the SE API (i.e. there are other types of responses which also indicate rate limiting). For the request which MS was making, a deleted post will actually return data, specifically a flag option descriptor for the "in need of moderator attention" flag.
@SmokeDetector I wouldn't have a problem if SE chooses to block titles like this, but it's not spam or R/A (i.e. not really something we're looking to detect), so it's FP for us.
@tripleee I've cleaned up the erroneous entries, created a bookmarklet which will prompt you for a domain link ID to delete, which I posted on the original GitHub issue.
@RobertColumbia Fresh olives, juicy onions, shredded cheese (with the small side of the grater). Throw those plus the spammers into a griddle and fry with butter. Butter the bread and toast under the grill for 5 minutes.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add the pattern you entered.
@Makyen On its own, it might just be a low-quality question, but given that the website has been spammed before, I'm not inclined to give it the benefit of doubt.
