[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, bad pattern in URL body, blacklisted website in body, +1 more: Enduraflex reviews by Testo ultra on askubuntu.com
So at what ballpark TP/FP ratio should we be adding things to the watchlist? In other words, I tend to go to metasmoke and search/test regexes prior to considering them for addition, and to be able to tune them for either wide detection, or a high TP/FP ratio.
obviously, if a watch creates a lot of noise, we will probably remove it; that's part of the deal with very relaxed criteria -- easy to add, but also easy to remove
is there something in particular you would like to experiment with?
Yeah, the thing that can't be determined form MS is how something will match against all the posts which aren't in the MS database, which, of course, is the vast majority of posts.
@Makyen I ran findspam.py locally for a while when there was something I was unsure of, that seemed to work pretty well for figuring out whether something was extremely FP-prone or not
we should probably make this easier or at least document how to do it though ...
@tripleee IMO a host probably shouldn't cut a site for spam unless it's coming from the same IP address. After all if it was a common practice and I had a competitor I could just spam their site all over SE knowing it might get them shut down while also getting deleted so fast it wouldn't give them any benefit.
@PeterJ that's a huge loophole for anyone who wants to spam, we all know that the spam economy specifically works through a lot of plausible deniability etc etc; but as you say, they should probably not cut them off just on the basis of a single complaint
would it be useful if I posted the correspondence I have had with Budgetnode to Teams? I feel the visibility might be vaguely useful to someone but I don't want to clutter the site too much
I'm thinking I would post a "question" about what is being done to track Babasupport and then the correspondence as an individual answer ... but my main question is whether it's worth the effort
@Magisch I got that, but I think it's too broad -- one per incident is more manageable IMHO, and will naturally float to the bottom of the pile when that particular event is no longer topical
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, link following arrow in body, pattern-matching website in body, +1 more: IS IT SAFE TO USE? by Fretty 19 on drupal.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body: The Body Building Plans 03 by Ritawhite on drupal.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, link following arrow in body, +2 more: About Vidhigra Supplement: by Wiltoped 19 on workplace.SE
@Makyen I remember that one, it was a bit of a borderline case. I was leaning towards spam, but the general consensus when I asked around in the Tavern was that we should simply close it as they're a student, not some commercial marketer trying to do market research
@angussidney I understand wanting to go easy on the person, despite that they really should have known what they were doing was a bad idea. I don't really agree with the "not a commercial marketeer" argument, as a considerable number of these types of requests are sourced from academics, rather than commercial. It's also not clear to me that SD/MS should be considering it fp, even with leniency for this person. I'd guess that comes down to: would we want a system level block?
[ 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: This is a trademark substance by Coles1961 on askubuntu.com
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +3 more: maxxmalesite.com/fxx-me/ by wsmlxwsvah on meta.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, link following arrow in body, pattern-matching website in body, +1 more: Lunatrim>Lunatrim>Lunatrim by wilfrdon on askubuntu.com
@micsthepick subject to correction, I'd say it would have been simpler (and perhaps lighter in processing load?) to watch "braindump" as smokey matches anywhere in a string.
I noticed that I can only perform certain actions such as commenting a finite number of times in a given period of time. Obviously, rate limiting is in place to prevent accidental misuse or intentional abuse of certain features.
Where else is rate limiting applied on Stack Exchange sites, and wh...
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +1 more: Master Testo Pro The non by user811844 on askubuntu.com
@tripleee That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
CI on d8d1179 succeeded. Message contains 'autopull', pulling...