Metasmoke instability continues, harming Smoke Detector (incl autoflagging), userscripts, and etc. We are unable to take any quick action, but are considering our options. If you have clever ideas, please add them as a comment on issue #257
So, I am now a mod on Aviation.SE. The thing is that I volunteered my account to the Charcoal system. I remember something about not doing it if you're a mod. Is it still the case? How do I revoke access to my account in such a case?
I guess he means you cast a manual flag when autoflagging isn't happening, but when MS does the autoflagging, it's not like you can influence whether it will cast one on your behalf much
it selects the flaggers randomly from a rather large pool of users
@tripleee So you want to tell it's MS job to cast autoflag than SD itself? Yes it does, when MS is down no autoflags will cast & we need to open offending post links manually then flag them.
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +3 more: x4up.org/alpha-muscle-complex/ by kwqs on astronomy.SE
[ 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: Youthful Balance Serum by TeamNZ 4 on meta.SE
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +4 more: x4up.org/alpha-muscle-complex/ by ayqs on askubuntu.com
the other rules (title and ... user name?) are not that stellar but also not all bad
they are a major provider so there will be FPs from time to time
but last time I checked this was in the top 20 among the active rules (almost top 10, and definitely top 10 among the ones with many recent hits)
"hosted by" is not entirely accurate, it triggers if the NS record contains namecheap, so they could have their name server on Namecheap and still their web site in completely different IP space
which perhaps we should actually check if FPs start to become a problem
Halflife has statistics going back but the logs are not in a convenient form; I should fix that but it's still an experiment for when I have nothing else to do
hard to tell from those results alone because it only sees the messages which were already flagged; it's possible that there are a lot of dormant FPs but it has worked better than I expected so far
@AjayBrahmakshatriya exactly, but the FPs could be different
soon everyone will be behind Cloudflare and then this won't work any longer
1. [:40347139] <skipped> 2. [:40347138] <skipped> 3. [:40347132] <skipped> 4. [:40347131] That message is not a report. 5. [:40347130] That message is not a report. 6. [:40347128] <processed without return value>
@AjayBrahmakshatriya probably yes, but if we can see that they remain reasonably static we can probably build a list of similar confidence as the current "bad NS" even if there is theoretically a large number of possible FPs
@tripleee I am not sure I understand completely. This list is recent 300 hits on the "bad NS" rule from the cloudflare IPs, right? If they remain constant what does that imply?
[ SmokeDetector | MS ] Bad NS for domain in body, blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: the genuine pack. The trial pack by Hi said on drupal.SE
