@Mast Yeah, that one gave me trouble as well, but was fixed on reloading. FWIW, the FIRE popup on the latest report metasmoke.erwaysoftware.com/post/413127 won't open for me, even after reloading the page, so there does seem to be something odd going on.
@SmokeDetector Text of answer is copied verbatim from the linked website, and doesn't really answer the asked question. It looks purely like promotion for the linked site.
@JeffSchaller I've added more rationale to the MS report. And yeah, it may not be obvious. Perhaps a custom flag with the reasoning would be better? (I already spam flagged it).
@cigien That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, blacklisted website in body, potentially bad asn for hostname in body, potentially bad keyword in body (295): How to Convert PST to MBOX for Free? by roggessteave on stackoverflow.com
@Pilot6 The "link at beginning" and "link at end" detections are not content-aware, but I'd personally like to see at least a couple of additions to a whitelist for them. The most notable of which would be i.stack.imgur.com. The same goes for linked punctuation, because lots of new users struggle with the link markdown and we end up getting an FP because of it. So... While it would be nice if we did this, it's not currently built, and getting someone to take the time to do it is difficult.
Especially when the reward is just a few less FPs, which are easily dismissed by giving them FP feedback.
