[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: have wonderful excessive hopes? by privtashelly on drupal.stackexchange.com
[ SmokeDetector ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: yoursbetterhealthsolutions.com/alpha-prime-elite/ by ChrisThompsonn on graphicdesign.stackexchange.com
there's an anti-spam paper from maybe 10 years back about the futility of this, basically they found that capturing "viagra" with high recall would also ruin the precision to the point where they also caught "niagara"
@Mithrandir I've added you, however I request that you (re-)read the feedback guidance page before you do anything to make sure you know what you're doing :)
[ SmokeDetector ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post, blacklisted user: healthpluscogni.com/zyntix/ by ysel saki11 on apple.stackexchange.com
@Undo/@ArtOfCode: minor unimportant request, can you add @JanDvorak to the Userscripts team on GH so that it represents the people who actually have push access to that repo.
[ SmokeDetector | MS ] URL-only title, bad keyword in body, link at end of body, link following arrow in body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: maximizedmuscleideas.com/revived-youth-cream/ by figaguzifebo on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] URL in title, bad keyword in body, link at end of body, pattern-matching website in body, pattern-matching website in title: phytolyft.com/tvolve-reviews/ by user71295 on drupal.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, repeated URL at end of long post: How mighty product Care is? by dineyjibond on stackoverflow.com (@dorukayhan)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: Will you zyntix assume that by Deverecter on workplace.stackexchange.com
angus posted some stats yesterday, the average has decreased 10 seconds (which doesn't sound like much, until you realize how much it takes to sway the all-time average by that much)
I think what's causing the average to be so high is the fact that during offpeak times there aren't many people around to give feedback/flag, and hence no action is taken on many posts
We should probably be removing outliers from those stats
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, link at end of body: blogmium.com/alpha-prime-elite/ by NicoRodrig on workplace.stackexchange.com
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: healthpluscogni.com/zyntix/ by user218478 on apple.stackexchange.com
[ SmokeDetector | MS ] Few unique characters in answer, no whitespace in answer, repeating characters in answer: Cannot save shipment by ffff on magento.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title: Perfect Youth Serum by emmiekauffman on workplace.stackexchange.com
@MarkYisri you can just flag, that's helpful enough. Check if your judgement of posts reported by Smokey are the same as those of the regulars. After a while, you can ask for privileges. At least that's how I did it.
@SmokeDetector account suspended now so unlikely to be necessary any longer
and the post was mod deleted
@MarkYisri it would be extremely nice if the whole thing could be ported to Python 3 before 2020 but being able to test things requires some amount of infrastructure (your own metasmoke instance and/or API key and/or other resources)
I think we're gonna hold off on porting to 3 until we're happy with autoflagging - one big project at a time, and all that. There are various issues that could be worked, though.
@MarkYisri what about it, in particular? The TL;DR is that we have a hell of a lot of data, and we decided to make use of it to enable us to flag spam posts automatically
Theorethically when the SE team approves there is nothing stopping us from upping flag count to 3-4 and make very short work of lots of spam with minimal effort.
@YvetteColomb you can't, at the moment - we don't have SE approval to cast more than one flag on a post, so it's running under my account so that we're not adding extra flags.
When registration opens, the registration status indicator on the dash will go green, and the preferences link is the one you want to actually start using it
When viewing your own flag history, I feel it would be valuable to show what percentage of flags have been marked as helpful.
I've implemented this as a userscript but would like to make a formal feature-request.
This is the result I came up with.
Feature Request Ideas
Change the percenta...
@tripleee how about excluding "at" in front. If you exclude posts with "at" prepending the "University of" from the list, you grab out most false positives: metasmoke.erwaysoftware.com/…
@Undo I can't figure out how, but it'd be nice if users were able to log in to metasmoke without the reviewer role - add a check for it before authorizing review, but allow login without it
@ArtOfCode Someone I know on SU has been flag banned (on a single site I presume), which prompted this question - will SD cope with this when auto-flagging is using individual accounts? Is there code in there to nicely handle this edge case?
@DavidPostill sort of - the flag on their account will fail, but Smokey will just keep trying other accounts until it fills the required number of flags or runs out of accounts to try
@ArtOfCode Have we gotten a declined flag from autoflagging yet? (I assume "fail" in the status means the system was unable to issue the flag, not that it was declined)
@Magisch you assume correctly. I don't think we've had any declined. I haven't checked every site, but I've checked the flag logs, and if a flag on any of those got declined I'd question the mods rather than the system.
Bruh, Dis Ting aint worth it. Mans gotta get his work dun. dat wont happen wid all this big fancy words. dum it down a bit bruv.
When viewing your own flag history, I feel it would be valuable to show what percentage of flags have been marked as helpful.
I've implemented this as a userscript but would like to make a formal feature-request.
This is the result I came up with.
Feature Request Ideas
Change the percenta...
