@doppelgreener I think with the current fake support number campaign wave and how they manage to get below autoflagging threshold with posts which are clearly spam, we can and even want to be more aggressive than usual
I'll put in a block for the .co.za suffix for now, but I'm not clingy, we could simply remove this from the blacklist altogether if it continues to be problematic
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@EriktheOutgolfer Probably from a deleted MS user, then the SD one from the great duplication (I assume, but haven't checked). BTW: There's a "Something not right?" button on the MS post page (just below the title) that is specifically for reporting problems like this.
@EriktheOutgolfer Yeah, but there's (now) a review queue for admins that, I suppose, such reports go into. Assuming that the admins are using it, then one would think that would result in the problem being resolved expeditiously.
@Makyen nah, just something that made my OCD beep loudly :P since the button is per-post, I'm using it per-post too, and, if we only consider that single post, then it does feel a bit wrong, although I'm pretty sure the button isn't to be used only for ultimate urgency
@EriktheOutgolfer The button should be used for "Something not right?" on the post. I was talking (wondering) about you notifying admins here in chat for that post. It just didn't seam urgent enough to notify in here (post is 1 year old & you didn't provide feedback yourself indicating what you thought it should be, other than the FP already there).
