[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body: Votofel force ireland by nameliferod on meta.SE
1. [:41474633] <skipped> 2. [:41474631] <skipped> 3. [:41474627] <processed without return value> 4. [:41474601] That message is not a report. 5. [:41474596] <processed without return value>
@bummi some of the spammers I think copy/paste from multiple sources when they get burned for plagiarism. A section which is clearly copy/pasted I think is sufficient if it's otherwise clear that it's spam
@JarkoDubbeldam for just saying k/f/n from chat, "SmokeDetector privileges (SD)" is enough (see charcoal-se.org/smokey/Privileges) - you need reviewer when you want to use userscripts for flagging/feedback though.
@WELZ the message is clearly not appropriate, might be just a test post or whatever but we probably want to monitor this user for a while in case he is going postal right now
@tripleee That pattern looks like it's already caught by Bad ns for domain in body and Bad ns for domain in answer; use !!/watch-force if you really want to do that.
I'm not arguing whether this post was on-topic on Travel or not, but it was migrated to 3D Printing, where it most definitely is not acceptable. What happened, and what do we do to move it back?
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 17-23: zyklon Body - Position 17-23: zyklon Username - Position 17-23: zyklon
@quartata That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer; use !!/blacklist-keyword-force if you really want to do that.
The answer in this report [ MS ] demonstrates what should be a new rule: Link text shows a URL with a domain that does not match the href's domain. Such deception is almost always a bad-actor.
I'm looking at my flag count, and I see a couple 'declined' flags and a few 'disputed' flags, and I'm wondering: what is the difference between the two? I've had both disputed and declined flags where the action I expected from the flag was taken, so I can't quite nail down what they mean (other...
@Makyen I actually implemented that as a filter a while back, but it caught way too many fps -- almost all reports were someone accidentally botching a link.
It's a filter in FireAlarm, but Fire only watches questions, and not on all sites
@quartata yep, that was me. The -1 in my achievement inbox reminds me that I need to check if the answer really gets deleted. It serves like a kind of bookmark.
@Makyen good idea. We’ve tried something similar in the past where the whole URL had to match, but it got lots of FPs due to typos etc. But if we only check the domain that should work really well