[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, email in answer, pattern-matching email in answer, potentially bad keyword in answer (348): Can I pay my credit card? by kevlin Ericksson on ell.SE
[ SmokeDetector | MS ] Bad keyword in link text in body, bad keyword with email in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title, +2 more (201): What is the cost of IVF treatment in Delhi? by Vins Fertility on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, blacklisted website in answer, pattern-matching website in answer, potentially bad ns for domain in answer, +1 more (341): Recover Photos from an iPhone in DFU Mode by billydaisy on superuser.com
@tripleee 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.
[ SmokeDetector | MS ] Url-only title, bad ip for hostname in title, bad keyword in body, blacklisted website in title, pattern-matching product name in body, +3 more (496): ketoavis.com/total-enhance-rx/ by hgmqwdbmkugp on askubuntu.com
:54512815 I can understand the immediate urge to delete messages like this (I've certainly felt it a sometimes myself), but we prefer that you don't delete them. We all get ninja'd from time to time, or even just make mistakes. In general, we prefer to leave such messages in the transcript, unless they are overly offensive, personally offensive to/towards someone, or overly promotional (i.e. notably beyond what we normally see).
In other words, things like getting ninja'd, or doing a !!/watch which was done earlier, but you just didn't see it, are common and normal. Yeah, we do try to not duplicate such things, but it's something that happens routinely, and isn't held against you, or anyone else.
[ SmokeDetector | MS ] Pattern-matching website in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer, blacklisted user (152): HTML CSS Responsive paragraph tag by Preeta on stackoverflow.com
Is the flagging condition update system broken or something? MS has gotten slow after both times I've managed conditions xd Might be unrelated, but twice... need to make sure :')
@Zoe [:54513706] Potentially bad keyword in body - Position 300-561: buy a better one or I don't understand something?</p><p>I only tried Eutectic Solder, 5 tip were from same source 1 from other. I don't know brands.</p><p>Soldering iron is one of those cheep chinese variable temperature ones</p><p>Here's photo of it <a
[:54514004] Potentially bad keyword in answer - Positions 78-90, 613-625: calendly.com [:54514000] Potentially bad keyword in body - Positions 198-210, 285-297, 418-430, 665-677: calendly.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in username, blacklisted website in body, link at end of body, potentially bad ip for hostname in body, +1 more (386): Do you want to ask any question? by Pure Cut Keto on askubuntu.com
@Machavity That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.