@tripleee That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@CodyGray I expect this isn't going to do what you're intending. The 🐱👤 probably isn't considered a word character, so the [\W_]*+🐱👤 will never be able to match. Also assuming 🐱👤 isn't a word character, it's unlikely that the next character is going to be a word character, so the bookending \b is unlikely to match. I'd probably try cheat[\W_]*+sheet[\W_]*?🐱👤[\W_]*+.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Spevacus That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Laurel No, it wasn't detected or reported. If you're willing to undelete it, unlock, !!/report <post URL> it to SD, then re-flag as R/A (because you can't raise a second spam flag on it), that could be quite helpful. Alternately, if it's fairly clearly spam, then there might be contact information (e.g. URLs/links, phone numbers, email addresses, etc.) which you could tell us, so they could be added to the watchlist, or just add them yourself.
@Makyen it probably wasn't flagged automatically because they somehow managed to mess up all the formatting. There were supposed to be 5 links, 4 being images and one that was included in the markdown references but wasn't actually used
@Laurel I assume you mean add the information to the watchlist, which I've done above. The post itself can't be reported unless it's first undeleted. While reporting it is quite helpful, the important part is, usually, to add the things the watchlist which will result in the post being detected if posted again, which the above should accomplish.
@blackgreen Thanks for the blacklist proposals. That website only appears in MS once as a True Positive, and we typically require 5, with some exceptions, before promoting a website to the blacklisted websites list. Additionally, we do tend to leave out preceding www and stick to the site name and TLD.
!!/watch booksyeah\.ml
!!/close 7541 "Doesn't meet blacklist requirements, contains https and www before domain name"
In this case, placing this on the watchlist is a good start. It'll be reported any time it comes up in a new post from now on, and we can elevate it to the blacklist if it becomes frequent enough.
@Spevacus There was a bit more information available to mods there. I've now reported the 3 other posts. I agree we still didn't meet 5 threshold, but I think that was probably blackgreen's thinking was as far as blacklisting it.
Yeah. If you use AF, you'll probably want to unselect "flag" since it will immediately nuke the post. I wait until I see the report come through in chat to re-flag the post.
@blackgreen Both SIM - SmokeDetector Info for Moderators (install) and SOCVR's Request Generator also have the ability to report posts, but do so through chat commands, rather than the MS API. The Request Generator also has the ability to perform other similar commands which are related to the post or user.
[ SmokeDetector | MS ] Bad keyword with email in body, potentially bad asn for hostname in body, potentially bad ns for domain in body (57): French AI project by Hany Roushdy on ai.SE (@Mithical)
@HenryEcker I appreciate the reports! I know it can be annoying to undelete and rereport for yall so just know that I do greatly appreciate it, and thanks for following up.
