@Vickel yeah It all started in 2016 where I was admitted to the ER the first time, that took a week, at the hospital. Then in 2017 I was admitted again and put into a coma to get respirator help, I was sick for 2 months. After that they've given me everything that is available to keep it away. I have chronic astma
I lost 25 kgs of weight back then (55 pounds approximately)
> Numbers-only title, phone number detected in title ---------- Numbers-only title - Position 0-12: 093394-32725 Phone number detected in title - Phone number: 09339432725
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, messaging number in answer, pattern-matching email in answer, potentially bad keyword in answer (367): git lost master branch by Jane on stackoverflow.com
@micsthepick Most of the detections would not have been run, due to the author of the post, you, having too much reputation. See the max_rep which is set for each detection.
@micsthepick While I agree that quantifier should be possessive, I'd expect the actual impact to be minimal without text that specifically targets that. Even with such text, it should only backtrack once. Change made.
@VLAZ We would normally watch the specific identifier. The specific identifier could end up being moved to the blacklist, while the general domain is unlikely to, due to FP.
@VLAZ That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@Vickel I mean, maybe. It's certainly not a good look. It's possible that it's good faith, and it'll get roomba-d at this rate anyways so I kinda don't care what happens to it.
@micsthepick @Makyen I think this one is more important to attend to, unless you were already looking through MS to see what thresholds of context we need :)
