[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body (294): Green CBD Gummy Bears UK by dktrotshe on meta.SE (@Ollie)
@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 if you really want to add this pattern.
@SmokeDetector The user's profile indicates that this might be a real question from them (i.e. something they are actually interested in), rather than just a spam seed. It is, however, way off-topic and deletion/blocking is reasonable, IMO.
[ SmokeDetector | MS ] Link at end of answer, potentially bad keyword in answer, potentially problematic ns configuration in answer, username similar to website in answer, blacklisted user (201): General Website Security by Wab Route on superuser.com (@Ollie)
[ SmokeDetector | MS ] Potentially bad keyword in answer, potentially bad keyword in username, username similar to website in answer (69): Confused about cloud computing by V2Soft on superuser.com (@Ollie)
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, blacklisted website in answer, potentially bad keyword in answer (267): Relay contact ratings by Christopher on electronics.SE
@metasmoke @CodyGray It's a terrible off-topic unclear question, but I dunno that it's TP...best case, they were wondering about the website that they were going to program and figured SO would be a good place to ask.
@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 if you really want to add this pattern.
@metasmoke A good while ago, I was asked to drop the TLD on blogspot style watches. That said, I don't know if that's a fair reason to close this. I'll leave it to someone else to decide.
@JeffSchaller You can watch an expression like that, yeah. Folks typically use \W* or [\W_]*+ in place of spaces in order to catch cases where a spammer might use more than one space in between each word. For that watch, you could do: uphold[\W_]*+wallet[\W_]*+us
@Ollie That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body Append -force to the command if you really want to add this pattern.
@Spevacus Does FIRE Additional Functionality work for you in the chat transcript? Would make it a sight easier to watch items instead of hopping back and forth between the current date and yesterday.
It would also mean I wouldn't have to search to see if someone already watched it, as the command would be grayed out.
@Ollie No, it'll only be activated (by default) if you're viewing from the Charcoal HQ chat page (as in you're connected to chat and viewing the page you're viewing now).
I imagine it's because, in order to send the messages like !!/watch and etc. via the script, it requires you being connected and actually on this page. But I haven't dug into the code to determine whether that's the case or not.
