« first day (3110 days earlier)      last day (711 days later) » 

11:01 AM
[ SmokeDetector | MS ] Potentially problematic ns configuration in answer (1): Unable to Update Post when Changing Site URL‭ by Radiant Web Solutions‭ on wordpress.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Creating PDF works on Unity (Windows) but not on a android device‭ by Edward Morrison‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Wireshark: Cannot find frame type of packets ✏️‭ by Nguyen Huy‭ on networkengineering.SE
 
metasmoke is a little slow for me at the moment
 
[ SmokeDetector | MS ] Manually reported question (93): HP printer supports and HP Printer Installation‭ by zylith jeon‭ on stackoverflow.com
 
11:06 AM
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): scharp project isnot working with image and load them on datya base‭ by Hamed shahrezaie‭ on stackoverflow.com
 
If only I could set up a smoke detector on my phone, so I get less postal SMS spam
 
don't expect too much even if you manage to pull it off; many of our rules are very specific to our environment
 
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, link at end of body, potentially bad keyword in body, blacklisted user (365): Moving averages‭ by gold gold‭ on meta.SE (@Ollie)
 
yeah, I was thinking of changing the rules, I wonder if pythonista has the capability
 
11:14 AM
tpu- feedback received on [MS] Moving averages
 
[ SmokeDetector | MS ] Link at beginning of body (40): Where is the Best Study abroad Consultants in Delhi?‭ by Transglobal aman‭ on superuser.com (@Ollie)
 
it probably would not be able to delete messages from the app, but it would be interesting to see how much of smokey's code works from installing it with stash
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Why does my MacBook Pro 2019 shows up Google Chrome running on iPhone 4?‭ by Ben jonas9385‭ on superuser.com (@Ollie)
 
!!/watch transglobal[\W_]*+overseas
 
!!/watch wisemarket\.co\.nz
 
!!/blacklist-website wisemarket\.com\.au
 
!!/watch (?-i:^bran arizona$)
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +1 more (482): Binance Customer Service: +1[/844]^4241~275++ helpline_phone number‭ by HannahSchm‭ on stackoverflow.com
 
[ SmokeDetector ] GitHub Actions: success on 2975b30 by tripleee in the master branch
 
!!/watch gold-pattern\.com
 
@tripleee That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command if you really want to add the pattern you entered.
 
11:23 AM
!!/watch (?-i:^gold gold$)
 
[ SmokeDetector | MS ] Phone number detected in body (99): HP Printer Installation Error +1.855.209.4888‭ by ashley baldwin‭ on stackoverflow.com
 
!!/blacklist-number +1 855 209 4888
 
if that's actually a different campaign, boo hoo
 
11:27 AM
[ SmokeDetector ] GitHub Actions: success on aeda6f3 by tripleee in the master branch
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad keyword in answer, blacklisted user (73): What is the purpose of this hole on Wacom Intuos Pro tablet?‭ by Ben jonas9385‭ on superuser.com (@Ollie)
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Make Terminal Remember last visited folder after closing it on MacOS‭ by Andrea‭ on superuser.com (@Ollie)
 
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (290): Binance_Toll FreeNumbre +18﹀:4442︻412:﹀75 collecting transpilable methods‭ by attentionsk‭ on stackoverflow.com
 
!commands
 
11:42 AM
!!/help
 
@AndrewT. I'm SmokeDetector, a bot that detects spam and offensive posts on the network and posts alerts to chat. A command list is available here.
[ SmokeDetector | MS ] Bad keyword in link text in body, pattern-matching website in body, phone number detected in title, potentially problematic ns configuration in body, scam aimed at customers in title (355): Delta Airlines Reservations +1-800-240-0573 Phone Number‭ by bookairlinesticket‭ on stackoverflow.com
 
!!/blacklist-number +1-800-240-0573
!!/blacklist-website deltaphonenumbers\.com
 
11:44 AM
[ SmokeDetector | MS ] Bad ip for hostname in body, potentially bad asn for hostname in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (104): Bandar Togel Hadiah Terbesar 4D 10 Juta Okewla | Togel Online Terpercaya Hadiah Terbesar‭ by Okewla Togel Hadiah Terbesar‭ on stackoverflow.com
 
what does it mean for the api to send a backoff? (in the context of the FIRE userscript)?
 
The Stack Exchange API sends backoff requests, telling the client of the API (e.g., the userscript making API requests) to literally back off.
See also the SE API documentation on throttling, which covers backoffs and other types of throttles. (The SE API is very demanding about this, and gives you little slack.)
 
so, switch to tpu, instead of spam right :)
 
Oh, you mean because choosing "spam" submits a flag via the API, whereas "TP" does not? That won't actually work, because the FIRE userscript uses the API for other things, beyond just submitting feedback, I believe. (Haven't looked at the code in a long while.)
But generally a backoff is not a thing to be concerned about from a user perspective. As long as the script (or whatever client that consumes the API) handles it appropriately, it's all good.
 
11:53 AM
right.
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, obfuscated word in title, +2 more (582): Binance-[SUPP0RT]-Number +l.(844)~::424.~:l275 toll phone Free number‭ by Eifzgqjzyae‭ on stackoverflow.com
 
!!/bisect HELPLINE NUMBER
 
!!/blacklist-number +18444241275
 
@micsthepick A normalized version, {'18444241275', '8444241275'}, of that pattern is already on the number blacklist. You can use !!/bisect-number +18444241275 to determine which entries on the number lists match that pattern.
 
11:55 AM
@SmokeDetector why
 
Bad keyword in body - Positions 11-25, 85-99: SUPPORT NUMBER, Position 135-150: HELPLINE NUMBER
Bad keyword in title - Position 9-16: SUPP0RT
Bad phone number in body - 18444241275 found obfuscated; 8444241275 found obfuscated
Bad phone number in title - 18444241275 found obfuscated; 8444241275 found obfuscated
Obfuscated word in title - 'supp0rt' is obfuscated 'support'
Phone number detected in title - Phone number: 18444241275
Potentially bad keyword in body - Positions 3-18, 77-92: BINANCE SUPPORT, Position 117-150: BINANCE TOLL FREE HELPLINE NUMBER, Position 151-155: WE'm
 
!!/blacklist-website wlo\.link
!!/watch livetogelresmi\.com
 
!!/watch marvelbuilding\.com
 
11:58 AM
!!/watch-number +91-9949475552
!!/watch smrvinayiconia\.propladder\.com
 
@CodyGray An invalid pattern was provided, please check your command.
[ SmokeDetector | MS ] Username similar to website in answer (68): Structure and usage of the construction - BE of‭ by worklifeenglish‭ on english.SE
 
!!/watch SMR[\W_]*Vinay[\W_]*Iconia(?!\.propladder\.com(?<=smrvinayiconia\.propladder\.com))
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in body, +3 more (582): Binance Helpline Number (+1 (844) 424-1275) Ask Support Number‭ by Adrr4ei6yzcgtvp‭ on stackoverflow.com
 
!!/watch worklifeenglish\.com
 
!!/watch worklifeenglish(?!\.com)
 
!!/watch worklifeenglish\.com
 
[ SmokeDetector ] GitHub Actions: success on 513b260 by tripleee in the master branch
 
@tripleee 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 if you really want to add the pattern you entered.
 
!!/shut your face
 
12:01 PM
@tripleee No such command 'shut'.
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): How do map applications calculate travel times?‭ by theleis67‭ on webapps.SE
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (384): binance_support_number_184442-41275 helpline service‭ by Sjawaer‭ on stackoverflow.com
 
!!/watch ticketinghub\.com
 
[ SmokeDetector | MS ] Manually reported answer (94): How do map applications calculate travel times?‭ by jacob78‭ on webapps.SE
 
[ SmokeDetector | MS ] Manually reported answer (94): How do map applications calculate travel times?‭ by ryuk apple‭ on webapps.SE
 
!!/watch sailica\.com
 
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Using Nginx to serve Multi-tenant app with HTTPS‭ by Mhm0ud‭ on serverfault.com
[ SmokeDetector ] Blacklists reloaded at rev 1ccf41217 (SmokeDetector: Auto watch of sailica\.com by tripleee) (running on teward/Osiris)
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +2 more (483): 1 (844) 424-l.275 || Binance Support Number || How to Contact Binance‭ by Nawassbd‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +2 more (483): 1 (888) 6O1-1439 || Coinbase Support Number || How to Contact‭ by rekedo3595‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Link at beginning of body (40): Chart.js is ignoring tick stepSize [codesandbox]‭ by menelai‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +3 more (579): Binance «Support« Number +⇘1844424︽1275⇘ workflows on GHES #257‭ by bliss‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, obfuscated word in body, phone number detected in title, +2 more (482): BINANCE_HELP_NUMBER (844-424-I275) TOLL-FREE_PHONE_NUMBER‭ by Binasder‭ on stackoverflow.com
 
@SmokeDetector --why-- who? what? where? when?
 
@micsthepick Potentially bad keyword in answer - Positions 664-678, 782-796: lambdatest.com
[ SmokeDetector | MS ] Phone number detected in title, scam aimed at customers in title (189): QuickBooks Payroll Help Number [**.1.844.401.1232**]‭ by cefodss‭ on stackoverflow.com
 
!!/blacklist-number +1 844 401 1232
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): MS Project chart for multiple projects‭ by Peculiar Favour‭ on pm.SE
 
tpu- feedback received on [MS] MS Project chart for multiple projects
 
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in title (192): What are the benefits of organic matcha?‭ by SEOdetoxie dgtl‭ on superuser.com (@Ollie)
 
!!/watch detoxie\.in
 
12:38 PM
[ SmokeDetector ] Blacklists reloaded at rev 772336e62 (SmokeDetector: Auto watch of detoxie\.in by tripleee) (running on teward/Osiris)
 
@tripleee huh! I almost watched it, but was thrown off by: Pattern-matching website in body - Position 1533-1544: detoxie.in/
 
the website patterns are useful as such but we generally also watch and blacklist individual domains ... perhaps we should review this practice to avoid doubling down on the detection reasons, or at least consider whether watching brings any additional value
I have been a proponent of the theory that the patterns might change from underneath, but currently that looks like a fairly minor risk simply because that part of the code is such a jumble that nobody wants to touch it
but eventually we should refactor it so that we regain control over it
(so to spell out what I only half said, watching a domain even though a pattern currently also matches would make sense because we might refactor or remove that pattern)
 
I think you are pulling a Makyen and over-thinking/over-explaining. The way I read Jeff's comment, it was just that he already thought the domain had been watched, given the detection reason that appeared.
 
right; I couldn't find evidence of someone explicitly watching blah.in/ versus blah.in
 
The reason categories are a bit opaque
This one in particular is-weirdly hyphenated.
 
12:45 PM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +4 more (656): Binance Support Number +(1↹8444➣241➣275) Actions: macOS 12 (Monterey)‭ by sallysteeves2‭ on stackoverflow.com
 
as so to hopefullly slightly clarify, there's a bunch of multiple screenfuls of hardcoded regex in findspam.py which create e.g. these patterns
 
I'm guessing this means it's a "hard-coded" one inside SD -- which is fine -- I was just thinking that 5-6 of those hits would turn it into a blacklist, and so we'd want to find the right match. As long as the right thing happens, I'm all good :)
 
as long as metasmoke manages to extract the domain, we keep tabs of how many posts we have seen with that domain name, watched or not
 
12:46 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (4): Mobile Design for Mattress Measurement Scenario‭ by Laura Thomas‭ on stackoverflow.com
 
got it; thanks!
 
I always interpreted that reason more as a "we found a pattern that matches/looks like a website", making it an extremely generic reason. But it sounds like you're explaining something a bit different, @tripleee? So now it's my turn to be confused.
 
!!/watch (?-i:^Laura Thomas$)
 
12:49 PM
@CodyGray yeah, it looks at the URL and if it contains ... sex or drugs (or rock'n roll, I'm tempted to add) it triggers
 
I think github.com/Charcoal-SE/SmokeDetector/blob/… might be the baked-in regex that caused that reason to appear
 
yup, that's the one
 
Oh. So this is really more like "website, with matching pattern"
 
not just any pattern, a baked-in pattern -- not one from bad_stuff.txt
 
yes, exactly
 
12:51 PM
[ SmokeDetector | MS ] Mostly non-latin answer (49): What effect does \f have when applied to css?‭ by 有毒物质123‭ on stackoverflow.com
 
Right, exactly. Website matching a specific hard-coded pattern. I don't think that's clear at all from "pattern-matching website". I think "website, with matching pattern" is significantly more clear, especially when you already know that SD uses a series of regexes to match patterns of suspected bad stuff.
 
unfortunately, some parts of metasmoke will lose track if we rename a reason. I have a couple of reasons which I wanted to rename upon closer reflection but then that ends up creating unatractive pollution and losing track of the efficacy of the rule so far
but we might want to think about creating some supplementary documentation for the obscure ones
 
so we have "Pattern-matching website in body" (code-based; website looks naughty) vs "Potentially bad keyword in" (bad_keywords.txt; something seen in the wild)
 
the bad keywords apply anywhere, not just in a URL
there's also blacklisted_websites.txt which specifically applies to ... actually domain names, not web sites
with some caveats; you can match the path part of a URL too
 
12:58 PM
right; just trying to add some words around my/our understanding
 
@tripleee surely there are a sizeable amount of Laura Thomas's out there? poor Laura!
 
@tripleee Ugh, really? It doesn't use numeric IDs or anything? It actually does string comparisons on the reasons? :-(
 
@CodyGray there's an id but it needs to be mapped from the string reason emitted by Smoke Detector; the "why" information is just a bunch of text
@micsthepick six users with that name on Stack Overflow, but none of them have any rep ... and this is just a watch anyway
 
Ah, the mapping is supposed to be done at the presentation layer, not at the bot layer. :-)
 
1:01 PM
(I would have considered blacklisting if it wasn't somewhat likely to FP eventually)
 
[ SmokeDetector | MS ] No whitespace in title (70): awdawdwaawddwadwaadwdaw‭ by user1‭ on blender.SE
 
tpu- feedback received on [MS] awdawdwaawddwadwaadwdaw
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): How to run chrome in debug mode with current user profile?‭ by AbelTsh3047‭ on stackoverflow.com
 
e.g. Halflife's halflife would be easier too if the "why" information was somewhat more structured, but that's one of the places I'm scared to touch too much
 
1:05 PM
[ SmokeDetector | MS ] Few unique characters in answer (88): Pytorch: undestanding the gradient of a function of tensors ✏️‭ by flawr‭ on stackoverflow.com
 
@SmokeDetector v
 
[ SmokeDetector | MS ] Link following arrow in body, potentially bad keyword in body (97): My ChartJS Line needs to click the color legend first before it plots the data‭ by Dos‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, potentially bad keyword in body, +1 more (394): Binance Support Number (1^(84+4) * 42 + 4)^1275 context free?‭ by weighsignifican‭ on stackoverflow.com
 
teward/Osiris: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev a6024ead1 (SmokeDetector: Auto watch of (?-i:^Laura Thomas$) by tripleee) (running on teward/Osiris, Python 3.8.10)
 
ha ha, clever attempt
 
Restart: API quota is 21482.
Makyen/EC2-linux: Executing automatic scheduled reboot.
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +3 more (579): Binance Customer Care Number +⅟844-424-1275 ♩ΣAγ♩ HelpLine_Phone_Number‭ by Kasldert‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (290): Binance (customer_support) phone 1-84442412-75 technical phone help number‭ by Jasdertg‭ on stackoverflow.com
 
1:43 PM
[ SmokeDetector | MS ] Bad keyword in link text in answer (81): Attaching a skull cap back to the head‭ by Mdsharif Ul Islam‭ on blender.SE
 
tpu- feedback received on [MS] Attaching a skull cap back to the head
 
!!/watch newtimeshair\.com
 
[ SmokeDetector | MS ] Potentially bad keyword in username (1): Data Science Podcasts?‭ by Skill slash‭ on datascience.SE
[ SmokeDetector | MS ] Link at end of answer, potentially bad ns for domain in answer (62): Data Science Podcasts? ✏️‭ by john carpenter‭ on datascience.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How can remove the "0" and "+" from the phone number in php‭ by Deepu‭ on stackoverflow.com
CI on 2450dfa succeeded.
 
[ SmokeDetector ] GitHub Actions: success on 2450dfa by tripleee in the master branch
 
!!/watch metam\.tech
 
[ SmokeDetector ] Blacklists reloaded at rev 13045051e (SmokeDetector: Auto watch of metam\.tech by Spevacus) (running on teward/Osiris)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Problem with bootloader / loop on the boot loader unlocked warning‭ by rbrtzlt‭ on android.SE (@AndrewT.)
[ SmokeDetector | MS ] Bad keyword with email in body (55): Error while debugging on andorid emulator or mobile device in flutter‭ by Geek‭ on stackoverflow.com
 
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 4dd95f541 (Makyen: Ping Makyen for some new metasmoke users) (running on Makyen/MS-Relay, Python 3.8.5)
 
@PeterJ Post 1: Already recently reported [ MS ]
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Hyperrefs from scatter plot to text‭ by Alexander Boll‭ on tex.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Exclusão de dados PHP‭ by João Desiderio‭ on pt.stackoverflow.com
 
fp- feedback received on [MS] Hyperrefs from scatter plot to text
fp- feedback received on [MS] Exclusão de dados PHP
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): C# Selenium navigate to Statistics on specifig Page‭ by Dragon‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Loading HF stock data into excel‭ by Steve Fagan‭ on quant.SE
[ SmokeDetector | MS ] Bad phone number in body, bad phone number in title, phone number detected in title, scam aimed at customers in body (366): SoUtHwEsT AiRlInEs +1 810-339-9515 ReSeRvAtIoNs nUmBeR‭ by Aileen Bruen‭ on stackoverflow.com
 
2:36 PM
@micsthepick @CodyGray The released version of FIRE uses the MS API for flagging. FIRE reporting a backoff from flagging means that the AWS Lambda container which did the actual SE API calls in order to flag received a backoff. That backoff was then forwarded back to MS, which then forwarded it back to FIRE, which reports it to you. From a user's perspective, it means that you should wait the specified number of seconds prior to flagging again through FIRE.
The following is some general background information on SE API backoff and rate limiting, which is helpful to know if you're working with the SE API, but may not be of all that much interest to you, if all you're wanting to know is what to do when FIRE displays a notice about getting a backoff (which is, don't flag through FIRE for that many seconds).
The SE API sends a backoff as one of the methods it uses for request rate throttling. Receiving a backoff value in the response from the SE API means that everything on your IP address should wait that number of seconds prior to making a request to that specific SE API endpoint/method/route. It does not apply to other endpoints/methods/routes, just the one you received it on, but it applies to everything on your IP address.
It does, however, tend to indicate that the number of requests seen from your IP address is a bit high, but can also just mean that the SE API is generally experiencing high traffic at the moment.
Unfortunately, the design of this aspect of the SE API assumes there's only one application on the IP address which is making requests to that endpoint/method/route. That is commonly an inaccurate assumption, except in relatively rare situations like SD instances, where there's usually only SD making requests from that IP address. If the IP address violates the backoff request, then the SE API can get upset and impose a longer delay during which it just returns errors.
[Note: this can make running a test instance of SD from the same public IP address as you're trying to browse SE ... interesting. :; ]
Given that a large portion of the use of the SE API is via userscripts, that people tend to use multiple userscripts, that there's almost never any coordination between different userscripts, and often no coordination between different instances of even the same userscript running in different tabs, this can result in lots of SE API accesses to the same endpoint/method/route from effectively independent code, but all from the same IP address.
This results in a situation where if there is throttling, it can fairly quickly cascade to being a block by the SE API, because the effectively independent actors have no knowledge that they are supposed to be throttled/a backoff was sent to the IP address, so they just go ahead and make requests. That all doesn't take into account the possibility of multiple browser instances on the same machine, multiple machines being in use, and/or multiple people sharing the same IP.
The SE API also has a few other layers of rate limiting. These primarily just return one of a variety of errors. These can be invoked without first having gotten a backoff, so code also needs to account for the possibility of just getting one of those error responses and delay making further requests in order for the SE API to see a "cooldown" of the requests from that IP address.
 
tldr: when it says to back off, you should back off?
 
@micsthepick Yeah, the TL/DR is the first paragraph, but even that can be boiled down to one sentence: "if you get a backoff from FIRE when flagging, then don't use FIRE to flag for that number of seconds."
 
[ SmokeDetector | MS ] Mostly punctuation marks in answer (36): Como comparar elementos de dos arrays JavaScript?‭ by Suso‭ on es.stackoverflow.com
 
2:53 PM
I'd note that MS should be imposing compliance with that backoff, but it doesn't. That's one of the reasons why MS ends up hard rate limited wrt. flagging, particularly if there's a lot of autoflagging happening.
 
[ SmokeDetector | MS ] Bad keyword in link text in answer, potentially bad keyword in answer (82): Detect face different part using ARKIT‭ by Mdsharif Ul Islam‭ on stackoverflow.com
 
3:10 PM
@SmokeDetector tpu- undisclosed affiliation (probably visible in PII, per comment left by site mod). Repeat offender.
sdc watch finsheet\.io
 
[ SmokeDetector | MS ] Bad keyword with a link in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (83): VAT refund in Milan airport, where to do it?‭ by user128514‭ on travel.SE
[ SmokeDetector | MS ] Username similar to website in answer (68): Spark: convert string to Date‭ by Jack Pan‭ on stackoverflow.com
 
3:24 PM
fp- feedback received on [MS] Spark: convert string to Date
 
@SmokeDetector Article is from 2018, so not likely spam.
 
3:44 PM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, phone number detected in title, potentially bad keyword in body, potentially bad keyword in title (283): ALASKA AIRLINES BOOKING NUMBER☎️(8O1) 9O5-8OO3‭ by nodejs‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Show/Hide a div based to its data-attribute from dropdown selection‭ by Noware‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title, +2 more (483): CRYPTO.COM 1-8552-25.47.27 PRANAY CUSTOMER SERVICE PHONE NUMBER (TOLL FREE NUMBER) ✏️‭ by cadads‭ on stackoverflow.com
 
3:55 PM
sdc blacklist-number 1-801-905-8003
 
@cigien That pattern appears to be homoglyph obfuscated. It's better to use the non-obfuscated number. Perhaps try: !!/number (801) 905-8003 Append -force to the command if you really want to add the pattern you entered.
@cigien Deobfuscated: (801) 905-8003; deobfuscated and normalized: 8019058003
That pattern may be a North American number. If it is, please use a format which starts with an optional `1` followed by possible separator text and has the main number in the format `801-905-8003` where `-` could be a single alpha character or any `[\W_]*+`. Alternately, you can add the comment `(?#IS NorAm)` to the end of the pattern to force also using the alternate normalized form, or `(?#NO NorAm)` if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try
 
Wow, smart tool.
 
sdc test (8O1) 9O5-8OO3
 
> Bad phone number in body, bad phone number in title, phone number detected in title
----------
Bad phone number in body - 8019058003 found obfuscated
Bad phone number in title - 8019058003 found obfuscated
Phone number detected in title - Phone number: 801 9058003
 
Yeah the number-blacklisting overhaul that Makyen did is pretty awesome.
9
 
4:04 PM
now if only makyen can give me the code they've promised for over 2 years now
 
sigh very much, yeah. It would help if we didn't end up with so many "we need this now to handle an ongoing event" things.
 
if(os != 'Ubuntu') die('Smoke Detector prefers Ubuntu');
There you go
 
As to that code, I'm looking at breaking some things apart so there aren't as many dependencies to allow smaller portions be committed and actually make progress in the released code.
6
 
[ SmokeDetector | MS ] Few unique characters in answer (88): Stop JavaScript panel in Chrome from persisting?‭ by asd‭ on superuser.com (@Ollie)
 
[ userscripts ] GitHub Actions: success on d26ad20 by Glorfindel83 in the master branch
[ userscripts ] GitHub Pages: success on 386c561 by Glorfindel83 in the master branch
 
4:22 PM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title (481): Monero Support Number +1(202-980-7955) UPDATE APP‭ by cjznoqf2641‭ on stackoverflow.com
 
@Makyen ye having monolithic evil code is evil
 
@Makyen This would probably make it easier for others to pick up issues as well.
Experience tells me breaking up a monolith is a truckload of work though, so best of luck.
 
Yep, all of the above.
@Spevacus Thanks (all).
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title (481): Monero (XMR) Support Number 1-206-567-8440 ASK CONTACT‭ by cbwqdhk7416‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Big Cartel Contact Page - Captcha LIQUID Error‭ by user19190940‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword with email in body (55): Spring Boot: Setting up the Trading Platform‭ by Abhinav Chaudhary‭ on stackoverflow.com
 
!!/watch Karenwellsweb
 
!!/watch susanchandler\.wchurch(?:@buck\.com)?
 
@ThomasWard Two days ago or so MS was lightning fast. It's slow as molasses now. Did something happen or is the reboot simply overdue?
 
@Mast reboot is probably overdue
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, bad phone number in title, phone number detected in title (481): Monero (XMR) Support Number 1-2O6-567-844O Update Info‭ by his7665‭ on stackoverflow.com
 
MS eats resources crazy fast
 
4:41 PM
Well, it should auto-reboot in 1/2 an hour.
 
@SmokeDetector fp- This looks like a low-quality assignment dump, but it doesn't appear to be promoting anything, nor is it complete gibberish. While R/A flags may be sustained for this question on the site, it doesn't cross the threshold for tp IMO.
 
@cigien Looks like an advert for a job.
 
@Mast or right now
 
@Makyen That will probably fix it for a while then.
@ThomasWard Is this a fixable problem?
 
@Makyen @Mast oddly enough the thing rebooted at 1:15PM local time so idk why it's being slow. define "slow" though
 
4:42 PM
I know the reboots are a hotfix of sorts.
 
because it could be a network issue regionally
@Mast ask Undo, Art, triplee, and others, I don't know the MS internals well enough I just provide the infra
sounds like MS needs kicked a couple times a day now
@Makyen can i somehow blame you for this :p
 
@ThomasWard I wouldn't be surprised if my network is faster than the one MS is running on. I'm on 300+ Mbps fiber (measured).
 
gig downlink, 150Mbps uplink, tested this morning.
not fiber, but higher QoS than residential internet (Business Class networks)
landlords won't let me get fiber run into the building
 
I'm my own landlord. I get ridiculously low ping over fiber.
 
but again you need to define "slow" wrt metasmoke
 
4:44 PM
@ThomasWard Yep, you likely can. It's probably due to me trying to renew a spam wave. I really should do that shortly after MS reboots. The code is ... not very efficient and substantially too often it just fails.
 
like what's "slow" here
@Makyen ye i'll blame you
and kick it to two reboots a day
 
That's ... probably not a bad idea.
 
When MS is fast, a lookup takes 2 seconds. When it's slow, the same lookup takes a minute.
 
@Mast It doesn't look like a job advertisement to me. It may be copy-pasted from one, but without any contact details whatsoever, or the OP even mentioning anything about a job, I wouldn't call it one. Also, the watch you added looks like just an example used in some JSON object in the question, and it's unlikely that it's the intent to spam that email address in the question.
 
4:46 PM
That's a factor 30 difference.
@cigien There's an e-mail address in it. That's contact details.
 
@Mast Depending on what you're doing, that can also depend on what's been cached in Redis.
 
@Mast that's disk/resource usage and whether there's cache
and if it's right at a reboot the cache might not be filled yet
MS is an evil resource hog, it uses the largest chunk of compute second only to my LXD server which runs like 50 containers in it
 
@Mast I assume you're referring to this: ` Example of a trader JSON object: 1 ******* **d": 1, "name": "Elizabeth Small". "email": "susanchandler.wchurch@buck.com", "balance": 62.0, "createdAt": "2018-04-16 04:56:28", updatedAt": ""`? That really doesn't look like spam for the email address to me.
 
Buck definitely is an HR company.
 
4:49 PM
Sure, if you feel this is spam for Buck, that's fine. I just don't see it myself.
 
If I'd be any good at servers, I'd build a copy of MS to test against. But I'm absolutely terrible at it.
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (384): BRD Wallet Support +1(206-567-8440) Nunber Bread Wallet Info‭ by admf9380‭ on stackoverflow.com
 
Heck, last time I tried I couldn't even get the wiki on Rails.
 
@ThomasWard as fast as you drink coffee?
 
4:53 PM
@ThomasWard BTW: If you're not aware, the public MS dumps haven't been updated in a while. I think you're in the middle of working on dumps, so you're probably already aware of that, but I figured I should mention it, just in case.
 
@Makyen ye i'm still aware
been busy as sin
work and prep for my sister's wedding this weekend
i'll get to it Eventually(TM)
 
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, bad phone number in title, phone number detected in title, potentially bad keyword in body (384): BRD Wallet Support +1(2O6-567-844O) Nunber BreadWallet iPAD Coll‭ by bxadetz1973‭ on stackoverflow.com
 
@metasmoke k
 
OK. Don't worry about it. Real Life™ certainly takes precedence.
Congratulations to your sister.
 

« first day (3110 days earlier)      last day (711 days later) »