[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, bad pattern in URL body, link at end of body, +2 more: Eternol Vitality Serum by user386312 on meta.SE
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +2 more: growxlsite.com/vigoriax/ by user79150 on codegolf.SE (@Mego @quartata)
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: Relax for minutes every night by wfrehfmpd on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, +1 more: To lose weight while sleeping by wfrehfmpd on apple.SE
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-10: boxjitter Body - Position 1-10: boxjitter Username - Position 1-10: boxjitter
@tripleee I can't find it either. Since it has caused an autoflagging FP, it's probably worth debugging with a local Smokey instance (which I don't have).
And the question was "I have prank on my friend that i wanna run in background (program lang C++). Post all the diffrent ways you can make program run in background with C++."
Some friends and I made our first steps on a D&D 4e campaign. (It's the first time we've played D&D in years, since we've mostly moved onto different games that better suit the kinds of stories we want to tell.) Also I finished Fullmetal Alchemist: Brotherhood again, and played a bunch of borderlands.
I know a user from M&TV who was involved in serial voting. When he was suspended a couple of times for that, he unupvoted all his posts via a sock account. I noticed that pattern and thought that someone else is unupvoting, so I brought to mod attention. However, I realized it later that it was one of his socks when he was suspended again. Currently he is serving a year long suspension.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: preserve the fats tiers by telutelu on askubuntu.com
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, repeating characters in body, repeating characters in title, title has only one unique char: aaaaaaaaaaaaaaaa by Wojtek El on stackoverflow.com
Update: Kevin Montrose makes it happen
The hell-ban is no more! Long live the verbose, obnoxiously evident ban!
Kevin has implemented (more or less) the system described below. Flaggers with a recent (past 7 days) flagging history consisting of at least 10 handled flags where >= 10% of flags we...
@Undo Here's a root-cause analysis: Fairly few people have autoflag thresholds below 200. Fairly few people can thus be hit by posts that hit only a bad keyword in body and title. Thus the declined autoflags tend to concentrate on those
May or may not be worth adding a few words to that effect in the disclaimer... "Selecting low thresholds will result in your account being significantly more prone to false positives, do so at your own risk."
Kinda covered by the existing to an extent, though
@JohnDvorak This would increase our security, as someone couldn't add a common word to the blacklist, and use that to let smokey flag a few posts of his choose
@Magisch The best protection against that is basically !!/stopflagging, if this ever comes up, going to github, and removing the malicus entry is too slow (because CI) and still gives power to the attacker
@Ferrybig Yes, but the argument is that for someone to add a malicious entry they'd either have to be a code admin, or have their entry approved by a code admin
@CalvT븃 My worry is that a code admin doesn't realize that <word> is a common word in <language> and nearly everything on that language site gets covered in three flags each
@CalvT븃 Or have their account hacked by a zero day attack in spam post (maybe I an thinking to much in the "what-if" situations now, but seeing our security from an attackers point of view might give us steps to increase it)
The best case is if we can automate the watch -> blacklist process, then maybe have some sort of process based on the same thing where it reverts to watch after x consecutive fps
I'm sure MS could handle a script that generates a score for each watch and blacklist based on tps vs fps, and then moves them about based on those scores
That would require: - A spammer to know of us (maybe) - That spammer having a really high desire to shut us down (lol no) - That spammer at the same time having access to zero day exploits (LOL NO) - That spammer taking the time to learn about our blacklisting process to find something to do with a CA's MS or SE account (You wish)
More importantly, you're one of the very few non-core people with a weight lower than the default, so you're getting picked on a high proportion of the non-core flags below 280.
