@Stormblessed 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.
@Stormblessed In general, please only use fpu when you are specifically intending to put the user on the username whitelist. The only time this should be needed (i.e. done) is when the user's username is being caught erroneously by some detection. If the user's username is not being caught by a detection, then there isn't any benefit for putting them on the list and a small additional amount of computation needed to check every detected username.
Hmmm... There's also minor additional writes to the storage media implementing the file system on which the SD instance is running.
@Stormblessed This appears to be the SD report for that MS post. The issue appears to be that SD and/or MS were, at that time, not properly handling Unicode characters. The characters, as displayed, are what are served by MS through the API, so it's likely what's in the database. Reports/posts currently don't have that problem. I don't know when the issue was resolved, exactly, but it was between 2017-01-19 and 2017-02-08.
Warning: teward/Supergate: 10 latest connections to metasmoke have failed. Disabling metasmoke
Warning: Makyen/EC2-Windows: 10 latest connections to metasmoke have failed. Disabling metasmoke
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +2 more (497): mumybear.org/neuro-24/ by ellington260 on askubuntu.com
@Makyen 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.
@Makyen 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.
@Makyen 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 | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (888): supplecient.com/krygen-xl/ by qiltgdhx on security.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +6 more (789): supplecient.com/krygen-xl/ by hrjfimmdz on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body, +1 more (392): unmistakable amino acids, for example by Swity on apple.SE
[ SmokeDetector | MS ] Bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body (491): Coinomi Support Number by giphy mia on meta.SE
[ SmokeDetector | MS ] Url-only title, body starts with title and ends in url, link at end of body, pattern-matching website in body, pattern-matching website in title, +2 more (495): health2wealthclub.com/ by maorco on askubuntu.com
> Potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Potentially problematic ns configuration in body - Suspicious nameservers: all IP addresses for techconferrences.com are in set {'103.53.43.196'} Potentially problematic ns configuration in title - Suspicious nameservers: all IP addresses for techconferrences.com are in set {'103.53.43.196'}
@Olivia That post makes no attempt to indicate that it's a copy from the linked page. That's not just bad attribution, it's plagiarism, which is TP. In addition, there's no original content (i.e. it's purely a copy). The post has been deleted by a moderator.
@Makyen 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.
@Makyen I know, I mod-flagged it (because it's a deleteable offense anyway), but I wasn't sure what feedback was appropriate. I didn't see everything was copied though. Anyway, thanks - I've given feedback on it now
> Url in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Blacklisted website in body - Position 12-34: supportservicehelp.com Blacklisted website in title - Position 12-34: supportservicehelp.com Pattern-matching website in body - Position 0-30: https://www.supportservicehelp Pattern-matching website in title - Position 0-30: https://www.supportservicehelp
@SmokeDetector To me this is rude, and falls under "A reasonable person would find this content inappropriate for respectful discourse." It's really just a rant. It doesn't attempt to answer. At best, it's asking to confirm the answer that was given 6 years ago.
[ SmokeDetector | MS ] Offensive body detected, offensive title detected, potentially bad keyword in body, potentially bad keyword in title, toxic body detected (160): FUCK ALL YOU PIECES OF SHIT by bitchtits1134 on gaming.SE
