OK, logged out again. I feel as if some times it's related to leaving feedback through FIRE. But definitely not all the cases where I've been logged out.
> Pattern-matching website in body, pattern-matching website in title, potentially bad asn for hostname in body, potentially bad asn for hostname in title ---------- Pattern-matching website in body - Position 0-10: earn54.com Pattern-matching website in title - Position 0-10: earn54.com Potentially bad asn for hostname in body - earn54.com address 46.30.215.121 in ASN 51468 Potentially bad asn for hostname in title - earn54.com address 46.30.215.121 in ASN 51468
@Dragonrage That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in bodyThe regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@Dragonrage 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.
> Bad ip for hostname in body, bad ip for hostname in title, bad ns for domain in body, bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username, potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Bad ip for hostname in body - cyberconstableintelligence.com suspicious IP address 102.218.213.66 Bad ip for hostname in title - cyberconstableintelligence.com suspicious IP address 102.218.213.66
@Zoe That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
But yeah, my protocol for finding Discussion spam is 1) Check if user is blacklisted 2) Blacklist and watch stuff if not and 3) Say where it's from. Others may vary.
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@Vickel In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
:65753462 In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of `+`,`(`,`[`, or `{` immediately followed by a digit. Append `-force` to the command word(s) if you really want to add the pattern you provided.
