@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (47): What is flash Bitcoin by Avairy Parrots on bitcoin.SE
[ SmokeDetector | MS ] Chinese character in title, bad keyword in body, mostly non-latin body, mostly non-latin title (326): 喜农场不过是农场主郭的圈钱工具罢了q by caonm on android.SE
@Makyen That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answer Append -force to the command word(s) if you really want to add the pattern you provided.
Anyone know if someone has gone and ran SmokeDetector against what was posted during the moderation strike to see what spam, if any, is still up? Also, would that be useful? cc @Makyen if you might know
@cocomac We considered it, but chose not to do so. There's nothing currently within SD which would make it easy to pick out posts within a specific date range. It's, of course, possible to do, but code would need to be written.
@AndrewT. Notifications are kept on a per-SD instance basis. We recently switched instances to Cerberus, with the intent to return to the Thoth instance, but it hasn't happened, yet.
@Makyen Wouldn't it be possible via either (a) making another script with a websocket that feeds SmokeDetector posts from the data dump within that range or (b) by modifying SD to read the dump directly (to a dedicated separate room, of course)? Not sure which would be easier though. If you/others don't think it'd be worthwhile though, totally fine.
@cocomac It is, of course, possible, with at least a few different methods of implementation. We just decided to not expend the effort. That doesn't mean that you or someone else couldn't do so, if they wanted to. IIRC, there was a bit of discussion about it back then. You're welcome to go searching to see if you can find that context.
@tripleee A normalized version, {{'19037176241'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number +190/37/17/62/41 to determine which entries on the number lists match that pattern, which would tell you: Matched by +1 (903)717-6241 on line 1373 of blacklisted_numbers.txt: 19037176241 found normalized
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially bad keyword in username (4): Lie's third theorem via graded geometry by spammer on mathoverflow.net
@Cow That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
### ReadTimeout on teward/Cerberus at 2024-04-10T12:46:58Z: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Read timed out. (read timeout=10.0) File "/home/smokey/SmokeDetector/metasmoke.py", line 644, in get_post_bodies_from_ms response = Metasmoke.get('/api/v2.0/posts/urls', params=payload).json() File "/home/smokey/SmokeDetector/metasmoke.py", line 691, in func response = method(GlobalVars.metasmoke_host + url, *args, **kwargs) File "/home/smokey/.local/lib/python3.10/site-packages/requests/api.py", line 73, in get
@cocomac Please provide an adequate reason for rejection (at least 20 characters long) so the user can learn from their mistakes. Use -force to force the reject
@Cow I know that is true for !!/coffee, I didn't realize it applied here too. Still, silently ignoring it feels suboptimal. Also, SD should have done it after I edited it to remove the @ sign. TODO figure out why it silently does nothing at some point
@Cow It happening on coffee was something I wanted to dig into at some point. Making a GH issue might be worthwhile here as silently doing nothing is odd. That said, I lack context so determining if that is/was intended behavior would be needed
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad keyword in title, potentially bad ip for hostname in body, potentially bad keyword in body, +2 more (291): Buy Percocet Online by James O. Duke on meta.SE
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, bad phone number in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, +1 more (276): Nodejs crypto in typescript file by Auguste Klaus on stackoverflow.com
@SmokeDetector First of all, this does not answer the question, they suggest something completely different. Second of all the user is not registered, I'm calling promotion.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, bad keyword in body, bad keyword in link text in body, blacklisted website in body, +1 more (459): German Language A1 vs. A2 Level by Hitesh Patil on german.SE
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
