[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title (294): new >>>>>>> Hi q Keto by scgrtumbr on or.SE
> Potentially bad asn for hostname in body, potentially bad asn for hostname in title, potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad asn for hostname in body - www.email-helplinecenter.com address 167.88.124.191 in ASN 3842 Potentially bad asn for hostname in title - www.email-helplinecenter.com address 167.88.124.191 in ASN 3842 Potentially bad keyword in body - Position 9-33: email-helplinecenter.com
> Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer ---------- Potentially bad asn for hostname in answer - www.email-helplinecenter.com address 167.88.124.191 in ASN 3842 Potentially bad keyword in answer - Position 4-28: email-helplinecenter.com Potentially bad ns for domain in answer - email-helplinecenter.com NS suspicious ns2.tigerexpertz.com.,ns1.tigerexpertz.com.
@JeffSchaller Are you seeing a lot of posts with it that domain which aren't being caught? Metasmoke has only one post with it, but metasmoke has been down for a total of several hours over the last few days, so we could be missing several posts which SD reported in chat, but were not recorded by metasmoke.
@Makyen That pattern looks like it's already caught by Mostly punctuation marks in answer and Mostly punctuation marks in body; append -force if you really want to do that.
@Machavity I'm not surprised. You might want to link How to reference material written by others in your comment, as it describes the minimum requirements for quoting/refernecing.
@SmokeDetector This is plagiarized from here (thanks Machavity for checking) , but the OP has previously responded to comments by making changes in their answer, so we're continuing to nudge the OP in the direction of making an acceptable answer. Machavity left a comment directing them to the referencing requirements.
[ SmokeDetector ] Blacklists reloaded at [rev 5467320 (Makyen: watch: use [\W_]* instead of \s for 11000 dollars -autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/5467320) (running on teward/Supergate)
@Makyen I visited this page. it redirected me to this after clicking on Authenticate w/ write access. And then finally to this page which says We need your current password to confirm your changes.
@Kulfy FIRE is a userscript. It adds a fire button, 🔥, to Smoke Detector reports on chat pages. Clicking on the button opens a popup which shows the post and has buttons to give feedback or feedback+flagging. It also shows the why information, which contains the reasons why the post was caught. ... ninja'd
@Kulfy This page lists the userscripts which we have. You can also look through the GitHub repository. For feedback & viewing in chat, I find FIRE and AIM to be the ones I use the most.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, repeating characters in body, repeating characters in title (386): XXXXXXXXXXXXXXXXXXXXXXX ✏️ by Xxx Ddd on math.SE
@SmokeDetector @Kulfy I'm not seeing what makes this one TP. What am I missing? I agree that it's not good that the long URL contains campaign and tracking information (I've submitted an edit), but that URL just looks like what the URL the OP actually went to (i.e. it looks like they just copied it from their URL bar). The campaign tends to indicate that it was likely a Google search link.
@Kulfy Currently, FIRE doesn't allow you to replace existing feedback. You will need to either go to the metasmoke page and click on the new feedback you want to give (i.e. on the checkmark or X in "Add feedback: ✓ ✗" ), or provide the new feedback in chat.
