« first day (3363 days earlier)      last day (446 days later) » 

12:01 AM
[ SmokeDetector | MS ] Bad keyword with email in answer, email in answer, potentially bad keyword in answer (165): Recovering LTC coin sent to a BTC address‭ by jacalyn‭ on bitcoin.SE
 
[ SmokeDetector | MS ] Bad keyword with email in answer, email in answer, potentially bad keyword in answer, blacklisted user (235): help can I recover ltc sent to a btc address‭ by jacalyn‭ on bitcoin.SE
 
@Jesse Post 1: Already recently reported [ MS ]
[ SmokeDetector | MS ] Bad keyword with email in answer, email in answer, potentially bad keyword in answer, blacklisted user (235): Unable to transfer my BTC funds from app wallet‭ by jacalyn‭ on bitcoin.SE
 
12:05 AM
 
!!/blacklist-number +1 (682) 4229549
 
@Jesse You don't have blacklist manager privileges, but I've created PR#7528 for you.
 
PR#7528 ("Jesse: Blacklist +1 (682) 4229549") opened by SmokeDetector
 
!!/bisect Gurutechnicalx
 
@CodyGray 'Gurutechnicalx' is not caught by a blacklist or watchlist item.
 
12:12 AM
!!/approve 7528
!!/watch Gurutechnicalx(?:@gmail\.com)?
 
@CodyGray I've been trying to come up with a good expression for this for like the last 2 minutes 😅
I got (?i:guru\w*technical\w*@gmail\.com) but I'm not sure whether or not it's overkill.
 
Yeah, the regexes are a huge challenge. Basically, what happens is that after you hang out here for a while, you'll see patterns that we use over and over. So you can treat those as templates (either just in your head, or literally with some kind of notepad/userscript/tool) to fill out when needed.
And then, if you really hang out long enough, you'll actually learn what the templates/patterns mean, and you'll end up finding that you've gotten a lot more knowledgeable about regexes.
 
I already have a lot of regex knowledge, I'm just unsure how specific/generic you guys want them to be.
 
Generally we try to be rather specific and, ideally, performant because of how many we subject every post that comes in to. We have an absolutely unholy number of them. It's kinda wild.
 
12:17 AM
The \w*s were initially .* but I thought that might catch a couple unwanted false positives.
 
@Jesse So... the problem with that is that it needs the "@gmail.com" part, otherwise it'd likely result in too many false positives (because it would match anything containing "guru[\W_]*technical"). Since this is a specific email address, they aren't going to be able to mix and match it with different spacings, so there's little benefit in having that variability included.
@Jesse Ah, well, that definitely helps a lot!
We want them to be perfectly specific, so that they match exactly what they're supposed to match, but no more. :-)
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): CSS isn't updating past my index.html within VS Code for Mac‭ by A Soggy Crouton‭ on stackoverflow.com
 
If you see another spam post where they've got something like "gurutechnicaly" or "gurutechnicalxy", then the existing regex should be updated to make it less specific and enable it to match those new variations.
 
@CodyGray I did include the "@gmail.com" part. I know they can't very easily change the email address, but it is gmail so they could very easily create a new one with slight variations. Maybe I'm thinking too far into the future but that's what I was aiming for with that.
 
12:20 AM
Oh, also: everything defaults to being case-insensitive, so there's no need to specify (?i:.
@Jesse Sorry, yes, I knew that it was included as non-optional. I'm just saying that is not ideal.
 
Okay sounds good. I will try to remember that.
 
@CodyGray To be clear: It's not harmful to do so, but may throw some people for a loop when they go back to look at a particular expression, because what they'll be expecting to see is the i flag being turned off, because that's a common pattern.
 
@CodyGray Ohh you're saying the expression shouldn't require the "@gmail.com" part. Okay that makes sense.
Right, so the "@gmail.com" part should be optional, but if I were to do that then my expression would result in too many false positives to be viable. I got it. Just had to think about it a bit ;)
 
Yes, exactly. There are many ways that someone might obfuscate an email address, but most of the time, it won't include obfuscating the name portion. So making the "@gmail.com" part optional would catch the majority of those, without being overly generic and thus too much of a pain to type in or risking too many false positives.
 
Alright sounds good. I will keep that in mind. Thank you for the insight.
 
12:25 AM
There are, occasionally, cases where someone will show a willingness to obfuscate the heck out of an email address (e.g., guru technical x 'at' g m a i l 'dot' com), so we need to get a more complicated regex to account for that. But we don't usually jump to that unless there's a demonstrated need for it, because keeping things simple is usually better.
But note that even if they do gurutechnicalx 'at' g m a i l 'dot' c o m, we'd still catch that by making the "@gmail.com" part optional. Also, people tend to reuse the same name for other services, so if they happen to have the Twitter handle "gurutechnicalx", then a regex matching that with the "@gmail.com" part optional would catch that, too.
Granted, a lot of it is bordering on pure speculation, but informed by a history of doing this. There's rarely a "right" and "wrong". Sometimes you just have to submit the watch and... watch it a while.
 
Alright. So to recap: make the expressions very specific and adapt them as needed. Make them performant because there's a lot of them, and if you include platform-specific signatures such as prefixes or postfixes, make them optional.
Oh and they're case insensitive by default.
 
You shouldn't worry too much about performance. The main thing to keep in mind with respect to performance is not to introduce any extreme pessimizations, like catastrophic backtracking. In general, though, regexes should be written to match what you want them to match, not sacrificing that in the interest of performance.
If there are two equivalent ways (or nearly-equivalent ways) to write an expression, one that is reasonably performant and another that's not, obviously choose the one that's more performant.
But yes, making it specific and adapting it if/when necessary (as more evidence is accumulated) is generally the best strategy, unless you have a specific reason to believe that the additional flexibility is going to be useful.
 
@SmokeDetector Would this be r/a or just naa?
I'm leaning more towards just NAA because it isn't attacking anyone or using fowl language, it's just unhelpful.
But then again, if slamming your keyboard and posting the result as an answer is abusive, then maybe this is too.
 
tending to be R/A due to "your mom" insult
 
Referring back to this answer on Meta, it says "posts by new users that contain no useful content at all" are abusive so I'll go with that.
 
teward/Thoth: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 468cf14075 (SmokeDetector: Auto watch of Gurutechnicalx(?:@gmail\.com)? by Cody Gray) (running on teward/Thoth, Python 3.10.6)
Restart: API quota is 78725.
 
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started in standby mode at rev 6e4e67bc72 (tripleee: Typo in comment) (running on Makyen/EC2-linux)
 
1:36 AM
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): What sources provide a list of all academic topics?‭ by Nutan Bhandari‭ on academia.SE
[ SmokeDetector | MS ] Link at beginning of body, potentially bad ip for hostname in body, potentially bad ns for domain in body (43): What Is and How to Choose Non-Sterile Pipette Tips‭ by hawalab‭ on bioinformatics.SE
 
1:47 AM
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): Transform every all 5 rows to column‭ by shakeel‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, blacklisted user (73): Những Kiến Thức Cơ Bản Trong Truyền Thông Doanh Nghiệp‭ by laianhvui‭ on money.SE
 
!!/watch hawalab\.com
 
@Jesse You don't have blacklist manager privileges, but I've created PR#7529 for you.
 
PR#7529 ("Jesse: Watch hawalab\.com") opened by SmokeDetector
tpu- feedback received on [MS] Transform every all 5 rows to column‭
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Is using a database wrapper microservice an anti-pattern? ✏️‭ by joannava‭ on stackoverflow.com
 
!!/watch msintsol\.com
 
2:13 AM
@Jesse You don't have blacklist manager privileges, but I've created PR#7530 for you.
 
PR#7530 ("Jesse: Watch msintsol\.com") opened by SmokeDetector
 
!!/watch sdgroup\.vn
 
@Jesse 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.
 
2:24 AM
@IanCampbell Post 1: Already recently reported [ MS ]
 
!!/approve 7529
 
!!/approve 7530
 
2:25 AM
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, blacklisted user (73): what is difference between Sterile and Non-Sterile Pipette Tips‭ by hawalab‭ on bioinformatics.SE
 
!!/reject 7524 "No new TPs, I agree with tripleee that this isn't needed right now and that one TP isn't enough to justify it"
 
@cocomac PR #7524 is not created by me, so I can't reject it.
 
But... I made it. Goes and rejects it on GitHub
/cc @tripleee
 
But SmokeDetector didn't make it
 
2:32 AM
@IanCampbell Would this be considered spam? I personally don't see a reason to consider the included link as undisclosed affiliation. It doesn't quite answer the question, but given that I think it would probably be NAA. What's your thought process here? Just curious.
 
Perhaps a little corroborating evidence at metasmoke.erwaysoftware.com/domains/108013
 
@Jesse It appears to be undisclosed affiliation. They stated on another answer on Software Recs that they work for the linked site.
 
@Jesse The user disclosed an affiliation in their software recommendations answer. The combination of posts makes it clear they are only interested in promoting the website.
 
Ahh okay I didn't see the other post. After seeing that I agree.
 
I custom flagged the Software Recs one, but I was lazy and only spam flagged the Academia one because I know the mods there better.
 
2:35 AM
It makes sense, but I thought that possibly SD had been given GH permissions to also reject PRs by other GH users (I have privs to approve/reject PRs, but I wasn't sure if that applied to PRs by other users or just SD)
 
Also... as you see more spam, you'll develop a better and better heuristic. A gut feeling if you will. =P
 
Next time I'll remember to check the other reported posts by the user when questionable posts like that come up.
!!/watch ldtalentwork\.com
 
@Jesse You don't have blacklist manager privileges, but I've created PR#7531 for you.
 
PR#7531 ("Jesse: Watch ldtalentwork\.com") opened by SmokeDetector
 
!!/approve 7531
 
3:12 AM
[ SmokeDetector | MS ] Link at beginning of body (41): IT Support wifi system 租Ipad 租notebook‭ by Peter‭ on stackoverflow.com
 
!!/watch insighthk\.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): PHP form is falling through the first if($_POST)‭ by surfturkey‭ on stackoverflow.com
 
@Jesse That's definitely rude/abusive. In addition to being content-free, it also contains an insult.
 
3:25 AM
@SmokeDetector ignore-
!!/watch hawalab(?!\.com)
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Help understanding this diatonic scale‭ by administr4tor‭ on music.SE
 
!!/watch 1p\.com\.hk
 
3:33 AM
 
!!/watch \s+systems?\.com
 
Oh whoops that's me. Does anyone know why that URL was flagged? I thought it was the official publisher for the manga based on the info in the first link I added to the answer
 
@Laurel The reason that was caught was "potentially bad ASN for hostname". That detection reason is definitely going to have some false positives. It doesn't necessarily mean that that's not the official publisher. The domain name itself was not watched.
 
As long as I'm not adding spam into posts lol
 
Makyen/MS-Relay: Executing automatic scheduled reboot.
 
Heh, no. I think if you were doing that, someone would have said something.
 
4:00 AM
[ SmokeDetector ] SmokeDetector started at rev 6b79b1731 (Makyen: Ping Makyen for some new metasmoke users) (running on Makyen/MS-Relay, Python 3.11.0)
 
Although, unfortunately, we do occasionally have some moderators editing spam out of posts. :-(
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): What does a red light on my circuit breaker mean?‭ by Mark Daniels‭ on diy.SE
 
!!/bisect galvinpower.org
Why is this watched when there were no prior TPs?
 
@CodyGray Matched by galvinpower\.org on line 47146 of watched_keywords.txt
 
4:21 AM
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (38): ListView, is there a simple way to allow dragging of items internally (built-in)?‭ by a deleted user on stackoverflow.com
[ SmokeDetector | MS ] Bad ip for hostname in body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (102): 6 Cách Giúp Phân Biệt Sữa Non Thật Giả Hiệu Quả Nhất‭ by user20568863‭ on meta.SE (@Ollie)
 
!!/watch bocavietnam\.com\.vn
 
@CodyGray 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.
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Please anyone guide me about the Redemption code?‭ by Mason Ethan‭ on stackoverflow.com
 
!!/watch kinegame\.com
!!/watch hyena[\W_]*+key
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): How Can I Pivot a Table in Microsoft Access?‭ by A.Solivera‭ on stackoverflow.com
[ SmokeDetector | MS ] Link at end of answer (62): Two keyboards. Can I re keymap just one?‭ by Bradley Neon‭ on superuser.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how we can make a dynamically download button in php‭ by Ummer Arif‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): unhandled promise rejection when running whatsapp bot ✏️‭ by Gabriel Dimas Eka Jaya‭ on stackoverflow.com
 
4:50 AM
!!/watch Spoof[\W_]*Paytm(?:[\W_]*Apk)?
 
[ SmokeDetector | MS ] Bad ip for hostname in answer, bad ns for domain in answer, bad keyword in answer, blacklisted website in answer (360): Alternative to Microsoft Office that does not require Internet or Cloud‭ by Hamilton Terry‭ on softwarerecs.SE
 
@SmokeDetector naa- This contains a disclosure of affiliation, so I cannot call it spam.
!!/bisect systemrw.com
 
@CodyGray Matched by systemrw\.com on line 46930 of watched_keywords.txt
 
5:19 AM
[ SmokeDetector ] SmokeDetector started at rev be8e092950 (SmokeDetector: Auto watch of Spoof[\W_]*Paytm(?:[\W_]*Apk)? by Cody Gray) (running on teward/Thoth, Python 3.10.6)
Restart: API quota is 76727.
[ SmokeDetector | MS ] Mostly non-latin body, no whitespace in title, potentially bad keyword in body (150): dsdasasdasddasasdadsasdasd‭ by kong dee‭ on meta.SE (@Ollie)
 
tpu- feedback received on [MS] dsdasasdasddasasdadsasdasd‭
 
!!/watch superc4
 
19 hours ago, by tripleee
!!/watch galvinpower\.org
 
Yes, I also used search to find that. What I did not easily find was why it was being watched when there were no prior TPs.
 
5:27 AM
Ask them.
If a moderators does that, it's usually based on a post that wasn't caught. But they're not.
Possibly based on information provided by halflife.
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): What is a decent wild camping tour in the desert?‭ by Arabian Oryx camp‭ on superuser.com
 
!!/watch Camp(?:ing|s)?[\W_]*in[\W_]*Oman
 
@Mast Yes, I was also able to figure out that the most convenient way for me to find out would be to ask them. However, this is not necessarily the most convenient thing for them, and since it's not really that big of a deal, I decided to do nothing. The watch is valid/correct and should stay in place, so no action is needed.
 
5:32 AM
@CodyGray there was a suspicious post reported yesterday metasmoke.erwaysoftware.com/post/410421
 
@cocomac Post 1: Already recently reported [ MS ]
 
@SmokeDetector Google translate says Thai gambling spam.
 
!!/watch superc4\.co
 
@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 word(s) if you really want to add the pattern you provided.
 
5:35 AM
@tripleee Ah, but no feedback. You weren't sure whether it was spam?
 
!!/unwatch superc4
!!/watch superc4\.co
 
!!/watch superc4(?!\.co)
@CodyGray exactly
 
Ah, how fun: they edited in the link after I already flagged it. :-)
 
5:35 AM
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Как задать правильно z-index?‭ by bxjdjd‭ on ru.stackoverflow.com (@USERNAMEGOESHERE)
[ SmokeDetector | MS ] Potentially bad keyword in body, blacklisted user (71): How to redirect all incomplete url to proper url (Related)?‭ by shahbaj rangrej‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in username (1): Planning To Relocate Abroad? Here’s What You Should Know‭ by helpxpat uk‭ on superuser.com
 
5:51 AM
!!/watch helpxpat\.com
 
@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 word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to get company details using Importxml from this URL?‭ by Sandy‭ on webapps.SE
 
this got two TPs but is still up; not really sure it's spam but definitely VLQ (MS) mathematica.stackexchange.com/a/279394
 
[ SmokeDetector | MS ] Pattern-matching website in body (95): The best boat rental in Canada‭ by Daniyal Afzal‭ on superuser.com
[ SmokeDetector | MS ] Link at beginning of answer (36): sum of count_over_time by day‭ by 李国忠‭ on stackoverflow.com
 
tpu- feedback received on [MS] The best boat rental in Canada‭
 
6:01 AM
!!/watch boatrentalscanada\.com
 
fp- feedback received on [MS] sum of count_over_time by day‭
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, username similar to website in answer (72): How to improve working processes between dev team and UX/UI designer? ✏️‭ by UIDesignz‭ on ux.SE
CI on 8b6412f succeeded.
 
[ SmokeDetector ] GitHub Actions: success on 8b6412f by tripleee in the master branch
 
!!/watch uidesignz\.com
!!/watch uidesignz(?!\.com)
 
[ 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, username similar to website in answer, +1 more (144): How to present a design to an internal client to gain their trust as a UI/UX designer for their company?‭ by UIDesignz‭ on ux.SE
 
@SmokeDetector uidesignz.com IP address adjacent to bitminerscenter.com; probably not enough to postulate a relationship between the two
 
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body, potentially bad keyword in body (43): which is the best bags brand?‭ by Optima Mart‭ on stackoverflow.com
 
tp feedback received on [MS] which is the best bags brand?‭
 
!!/watch optimabags\.in
 
@CodyGray 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 ] Potentially bad keyword in body (1): Как задать правильно z-index? ✏️‭ by bxjdjd‭ on ru.stackoverflow.com (@USERNAMEGOESHERE)
 
6:13 AM
another IP address in the same netblock ... raising suspicions
 
!!/watch Optima[\W_]*(?:Bags|Mart)(?!\.in(?<=optimabags\.in))
 
[ SmokeDetector ] GitHub Action workflow build (3.11): failure on 82b3372 by tripleee in the master branch
 
@SmokeDetector quite rude according to Google Translate
 
6:15 AM
Google Translate apparently translates the "Flag" link text on RuSO into "Anxiety" :-)
 
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): Как правильно ебать кчау? ✏️‭ by bxjdjd‭ on ru.stackoverflow.com (@USERNAMEGOESHERE)
 
!!/bisect NutRa
 
@CodyGray 'NutRa' is not caught by a blacklist or watchlist item.
 
@SmokeDetector tpu- Still rude
 
6:17 AM
[ 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, potentially bad keyword in username, +2 more (145): Building my UX Portfolio - Where to find Users to Interview?‭ by UIDesignz‭ on ux.SE
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad keyword in answer (2): Using Quietrock drywall AND Rockwool Sound Insulation?‭ by user162347‭ on diy.SE
 
[ SmokeDetector ] GitHub Actions: success on 5f3e1ce by tripleee in the master branch
 
6:26 AM
CI on 5f3e1ce succeeded.
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body (2): What are the most important concerns of users regarding pre-rolled boxes?‭ by Captain2022‭ on ux.SE
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Consumir api de WhatsApp‭ by Codimbo‭ on es.stackoverflow.com
 
[ SmokeDetector ] GitHub Actions: success on bbd9167 by tripleee in the master branch
 
[ SmokeDetector | MS ] Mostly punctuation marks in body (28): Как поправить код? ✏️‭ by user540455‭ on ru.stackoverflow.com (@USERNAMEGOESHERE)
CI on bbd9167 succeeded.
 
tpu- feedback received on [MS] Как поправить код?‭
fp- feedback received on [MS] Consumir api de WhatsApp‭
tpu- feedback received on [MS] Как поправить код?‭
 
6:37 AM
@metasmoke Twice? Stuttering again, huh?
 
Do we have a "hide images in MS reports" userscript? I believe there is one for SE, but is there one for MS currently…?
 
!!/unnotify-all-admin 414442
 
@tripleee I will no longer ping user ID 414442 anywhere when I report a post.
 
@cocomac my recollection is that the Gas Mask script would also block images in FIRE dialogs, if that's what you mean
I don't currently use it and I know some refactoring was done to FIRE in the meantime but AFAICT it should still work the same; after all, the image links are the same
 
I meant MS itself, but that’s good to know
 
6:45 AM
anyway, I only see "Click to show image" in FIRE so I guess it has a feature like this of its own now
@cocomac no images are rendered in metasmoke itself, or can you show where exactly you mean?
 
@JiminyCricket. I could be wrong, but I believe that happens when a user gives the first feedback on an MS report, triggering a chat message, they clear the feedback, and then someone else gives feedback on the same report, which triggers it a second time (as the original feedback is cleared)
 
@tripleee They are, if you click on the "Preview" tab.
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (4): As the summer season is coming, which should be the most comfortable bedsheet fabric in summer?‭ by kunalkapoor001‭ on meta.SE (@Ollie)
 
@CodyGray ah, yes, I see, of course
 
6:49 AM
Here’s one example of an MS report with images metasmoke.erwaysoftware.com/post/410582
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Magento 2 Adding Contact Us Page in CMS block not working‭ by Saad Ahmed‭ on stackoverflow.com
 
!!/blacklist-website rdtrend\.in
 
@cocomac Ah, a much tamer example.
 
6:55 AM
CI on 9ec202b succeeded.
 
[ SmokeDetector ] GitHub Actions: success on 9ec202b by tripleee in the master branch
 
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): ARE SEX TOYS LEGAL IN INDIA?‭ by 18careindia‭ on superuser.com
 
tpu- feedback received on [MS] ARE SEX TOYS LEGAL IN INDIA?‭
 
!!/watch-number 9988667918(?#NO NorAm)
 
@CodyGray 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 998-866-7918 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 !!/watch-number 998-866-7918. Append -force to the command word(s) if you really want to add the pattern you provided.
 
6:57 AM
!!/watch 18[\W_]*care[\W_]*india
 
@cocomac That would explain it. We've seen it before, didn't quite know what to make of it so elected to just be watchful. Seems like normal behaviour in that case. No worries, thanks for telling.
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Change wallpaper of window ✏️‭ by Scivic‭ on superuser.com
 
stackoverflow.com/users/8178927/user8178927 many answers recommending same library.. probably spammer
all answers
 
7:09 AM
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started in standby mode at rev 6e4e67bc72 (tripleee: Typo in comment) (running on Makyen/EC2-linux)
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Creating Group Chat Feature‭ by user8178927‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Third-Party live Chat API to frontend or backend?‭ by user8178927‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Broadcasting to everyone except sender socket.io‭ by user8178927‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Laravel and react native chat‭ by user8178927‭ on stackoverflow.com
 
@SurajRao thanks
 
[ SmokeDetector | MS ] Potentially bad keyword in username (1): ask the user to enter the amount of a purchase ✏️‭ by ffffffffffff‭ on stackoverflow.com
 
7:14 AM
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): How do i merge two JSON arrays from two seperate datasets into to one array in php ✏️‭ by nhtj‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more (483): Prime CBD Gummies Reviews‭ by primecbdgummiesget‭ on stackoverflow.com
 
tpu- feedback received on [MS] Prime CBD Gummies Reviews‭
 
7:22 AM
!!/watch brigadevalencia\.ind\.in
 
tpu- feedback received on [MS] Cannot install Wordpress‭
 
!!/watch valuecoders(?!\.com)
 
!!/watch brigade[\W_]*+valencia
 
[ SmokeDetector | MS ] Bad ip for hostname in answer, bad ns for domain in answer, blacklisted website in answer, potentially bad asn for hostname in answer (273): How to do Export Office 365 Mailbox to PST in a Effortless Manner?‭ by Malini Sinha‭ on superuser.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (71): React Native & Sendbird - invalid parameter‭ by user8178927‭ on stackoverflow.com
 
huh, did I miss one?
 
!!/report stackoverflow.com/a/74416733 "Appears to be undisclosed self-promotion."
 
7:27 AM
[ SmokeDetector | MS ] Manually reported answer (94): i cant implement pagination in flutter‭ by Ngonidzashe Mangudya‭ on stackoverflow.com
 
@tripleee A deleted one :-)
It was deleted through the review queues like 12 days ago
 
!!/report superuser.com/q/1766144/97118 "spam seed"
 
@CodyGray oh right, thanks for finding that
!!/dig www.shoviv.com
 
@tripleee 107.154.159.113
 
7:29 AM
!!/watch Export[\W_]*Office[\W_]*365[\W_]*Mailbox[\W_]*to[\W_]*PST
 
7:41 AM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Is it possible to book a specific seat on DB trains?‭ by David Harley‭ on travel.SE
 
!!/watch miserbee\.com
 
!!/watch miserbee(?!\.com)
 
7:47 AM
[ SmokeDetector ] GitHub Actions: success on 860b02b by tripleee in the master branch
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how to show action button on react google charts in ReactJS?‭ by ini indah‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword with email in answer, link at end of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (149): UK postcode validator‭ by Parry‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Proper structure for if else statement in mongodb query‭ by Swagat Das‭ on stackoverflow.com
 

« first day (3363 days earlier)      last day (446 days later) »