[ SmokeDetector | MS ] Few unique characters in body, luncheon meat detected, no whitespace in body, no whitespace in title, potentially bad keyword in body, +3 more (431): kkkkkkkkkkkkkkkkkkkkkkkkkkk ✏️ by Louis on stackoverflow.com
> Pattern-matching website in answer, potentially bad ip for hostname in answer, potentially problematic ns configuration in answer ---------- Pattern-matching website in answer - Position 0-21: https://sabtorotbe.ir Potentially bad ip for hostname in answer - sabtorotbe.ir suspicious IP address 185.141.168.43 Potentially problematic ns configuration in answer - Suspicious nameservers: all IP addresses for sabtorotbe.ir are in set {'185.141.168.43'}
@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.
@treyBake @ColumbiasaysReinstateMonica Unless you want to see the response from SmokeDetector confirming your feedback, you can append - to the feedback you're giving to suppress SD's response. Alternately, you can use one of the feedback aliases (e.g. f for fp-), which include suppression of SD's response. I'm not saying you need to do so, just that it's available.
@Makyen ohhh, that makes sense now.. I used to do the - but didn't know if it was actually working when I used it (now I know why :p) will definitely use to keep the chat room a bit slimmer
@treyBake Yeah, not having the assurance that the feedback was actually applied is the trade-off. To see that feedback has been applied, I primarily use AIM, which shows the feedback for each report inline with the chat messages. I find it gives enough information to be reassured that the feedback was actually applied.
@treyBake np. You might want to also check out FIRE, which adds a FIRE button to each report. Clicking on the button opens a popup which shows the post, the why information (when the post title in the poptup is hovered), and buttons providing the ability to give feedback and/or flag the post, etc.. Personally, I find it quite convenient.
@Das_Geek 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.
@Das_Geek 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.
@treyBake When you give the wrong feedback on a post, please either A) feedback again with the feedback you feel is correct, or B) go to the post's page on metasmoke (the "MS" link on each report takes you there), and "clear" your incorrect feedback. To do so, you'll need to click on the "(clear)" that is to the right of the list of feedback at the top of the post's page. This will take you to another page, where the feedbacks are listed and you can click on "delete" for your feedback.
If you give new feedback, it will replace your old feedback, if the old feedback was given less than 24 hours ago. If the old feedback was more than 24 hours ago, then you will need to clear/delete it.
@Das_Geek That pattern looks like it's already caught by Bad keyword with email in answer and Bad keyword with email in body; append -force if you really want to do that.
@SmokeDetector tp- because they are indeed affiliated with the product (they are CDMO of the company), but it does look like a genuine answer that doesn't just post content relating to the affiliated product. I commented on the post, no flag for now.
