Unfortunately, the capability to get a poster's network ID without incurring substantial quota was only recently added to the API, and the SD devs haven't yet had time to add new functionality that would take advantage of it.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body (291): Weight Loss Pill by biofit0 on superuser.com (@Ollie)
Hm. That does seem to have some FPs on the network. Let me check them out a little bit.
@cairdcoinheringaahing Not really, besides seeing what we chat about. There are some things we discuss outside of chatroom for the sake of privacy. There are no other benefits. To my knowledge, we do not require anyone to be in the Team or anywhere else to participate here in any role. Admins may be an exception as they've got additional duties but... They're admins, after all.
@cairdcoinheringaahing Should you be interested in joining the Team, you can do so by grabbing your metasmoke account's e-mail from here and pasting it into the modal you'll see from here. It's completely free (SE provides it for Charcoal for free) and, again, completely optional.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (4): A 60 year male is brought by his wife by paulbudd on superuser.com (@Ollie)
@tripleee 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 if you really want to add this pattern.
@tripleee That doesn't appear to meet the blacklisting requirements. I only see 3 hits in MS for that domain. None of those hits appear to have other already existing blacklist detections. Am I missing something?
it shares an IP address with mygreatlearning.com so I was thinking that would suffice to quality them as being in cahoots ... but looking at that now I see that the recent hits are FP
@tripleee np. Thanks for taking another look at it. I agree that if the other domain with which it shared an IP address was on the blacklist, then it would qualify as an ongoing campaign.
I must admit that's not something I check for, but I probably should.
I have been planning to update Halflife to add this information as it finds it but I have been putting off any major changes until I can finally pull of that refactoring I have been talking about for so long
Please check that both your flagging preferences and flagging conditions include all the sites on which you desire to be autoflagging. When SE adds a new site, your flagging preferences and conditions are not auto-updated to include the new site.
4
We just had an autoflaggable post be detected on Cardano with a weight of 337, for which nearly everybody wanting to flag on Cardano should be eligible as a flagger. There was a grand total of 1 eligible flagger with the Core role, and 10 non-core users (almost all were recently created, so had Cardano included by default). If it's been a long time since you checked both your flagging preferences and conditions, then there may be more sites which aren't in them.
There are currently 178 sites available.
Obviously, if you don't want to be autoflagging on a site site, then don't include it. If you do desire to be autoflagging on a site then you need: a account/profile on that SE site, the site to be in at least one of your autoflagging preferences, and the site to be in at least one of your enabled autoflagging conditions.
@Makyen That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command if you really want to add this pattern.
@CodyGray 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 if you really want to add this pattern.
@CodyGray 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 if you really want to add this pattern.
[ SmokeDetector | MS ] Chinese character in title, mostly non-latin body, mostly non-latin title, blacklisted user (312): 郭老欺穷途末路，战友须认清形势 by EdwinPowell on meta.SE (@Ollie)
@tripleee 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 if you really want to add this pattern.
[ SmokeDetector | MS ] Few unique characters in answer, no whitespace in answer (184): морской бой на с++ by lox on ru.stackoverflow.com (@VictorVosMottor)
@Xnero 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 if you really want to add this pattern.
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (202): Are there any Exipure AU side effects? by vedisamadilo on superuser.com (@Ollie)
