« first day (2932 days earlier)      last day (881 days later) » 
00:00 - 16:0016:00 - 00:00

4:00 PM
[ SmokeDetector | MS ] Bad keyword in body, obfuscated word in title, phone number detected in title (166): Quickbooks™+tech suppo'rt +1-866+481+0014 phone+number by xonebel on stackoverflow.com
 
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in title, phone number detected in title, several emoji in title (366): Quickbookss™ ❝1 (802) 800-2526❞ Enterprise Support Number@BUT$ by giluhi on stackoverflow.com
 
[ SmokeDetector | MS ] Link at beginning of body (41): Difference between lazy minting in OpenSea and Rarible by kris_bird on ethereum.SE
 
@SmokeDetector oh no they are ZALGO-ing us now... D:
 
4:12 PM
Keep that up.
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, bad phone number in body, bad phone number in title, +1 more (463): IN MANAMA < ASK DOCTOR JOY> +27640211696 ABORTION PILLS FOR SALE IN BAHRAIN (RIFFA ) &&*&^%%&QATAR HAMAD TOWN <<M<> MUHARAAQ CYTOTEC PILLS MISOPROSTOL by Doctor Joy on superuser.com
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, phone number detected in title (264): %"QuickBooks®"+I-866-48I-0OI4 Service+phONe %NUmBEr& by pobaca on stackoverflow.com
 
4:32 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Her face, a revolving door, swings open and shut, open and shut by Sasi on english.SE
 
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in title, phone number detected in title (269): (1-802-800-2526)Quick-books 'Technical' Support Number by lejeleny on stackoverflow.com
 
[ SmokeDetector | MS ] Link at beginning of answer (34): Wordpress image hidden sticky header by Urvik Moradiya on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in title, bad phone number in title, phone number detected in title (269): Quickbookss™ Technical Support❝1 (802) 800-2526❞ Number@Help$ by qokegogel on stackoverflow.com
 
4:45 PM
 
New metasmoke user 'rktech' created
 
@metasmoke I need activtion. Accounts require manual activation. Ping a metasmoke admin in Charcoal HQ (room 11540).
 
!!/watch seekhterahiye\.com
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Problem understanding a grub.cfg line with search.fs_uuid by Atul Vaish on askubuntu.com
[ SmokeDetector | MS ] Bad keyword with a link in answer, potentially bad keyword in answer, blacklisted user (153): Is coenzyme A a vitamin? by Harshit Tiwari on biology.SE
 
@Chris Post 1: Already recently reported [ MS ]
[ SmokeDetector ] SmokeDetector started at rev 2b0c5c9dc (SmokeDetector: Auto watch of seekhterahiye\.com by Cody Gray) (running on teward/Osiris, Python 3.8.10)
Restart: API quota is 18184.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Least affordable neighborhood in python by Potter on stackoverflow.com
[ SmokeDetector | MS ] Post is mostly images (19): Vector graphics: EAN-13 Barcode grade correction using JS library ✏️ by tarun on stackoverflow.com
 
5:43 PM
[ SmokeDetector | MS ] Link at beginning of answer (34): VSCode The terminal could not be started (exit code -1) by Oliwczak12 on stackoverflow.com
 
5:56 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Her face, a revolving door, swings open and shut, open and shut by Sasi on literature.SE (@Mithical)
 
[ SmokeDetector | MS ] Bad keyword in body, obfuscated word in title, phone number detected in title, potentially bad keyword in body (167): (QuickBooks-tech'nical +1-866-481-0014 help suppor't pho'ne number by gofige1798 on stackoverflow.com
 
6:28 PM
sdc watch hutwani\.com
 
sdc watch clickteam\.org
 
fp- feedback received on [MS] Customized url and page for SEO
 
[ SmokeDetector | MS ] Bad keyword in body, obfuscated word in title, phone number detected in title, potentially bad keyword in body, scam aimed at customers in title (267): 'QuickBooks%' Tech'nical +1-866-481-0014 Suppor't Pho'ne NUm'ber &*9% by vinopi8489 on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer, potentially problematic ns configuration in answer (2): How to preserve a rare version of a book respecting the copyright as well? by Roku Support on academia.SE
 
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): ocr.space JavaScript error and doesn't give out any output ✏️ by Abdelrahman Mohamed on stackoverflow.com
 
7:00 PM
[ SmokeDetector | MS ] Few unique characters in answer, repeating characters in answer (167): Is Colossians 2:16 addressing "ceremonial" Sabbaths only and excluding the "moral" Sabbath? ✏️ by Dave on hermeneutics.SE
 
@rktech Welcome! I'll ping someone for ya! ( @Makyen @tripleee )
 
New metasmoke user 'Jesse' created
 
7:15 PM
sdc watch user:15834359
 
@AdrianMole You don't have blacklist manager privileges, but I've created PR#6770 for you.
 
PR#6770 ("Adrian Mole: Watch user:15834359") opened by SmokeDetector
 
err... no.
!!/reject 6770 "That is not the correct way to watch a user account. That would add that string to the watchlist."
 
@CodyGray 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
@CodyGray Closed pull request #6770.
 
@AdrianMole No judgment, because I've surely typed stupider things into this box, but were you perchance trying to add a particular user account to the blacklist?
 
7:20 PM
I wanted to watch a user - two spammy posts out of two.
 
Apparently I'm supposed to ping an admin to activate my Metasmoke account. I'm not sure who here is an admin though. Can anyone help me?
 
@AdrianMole You need !!/addblu <userProfileURL>
 
@AdrianMole Manually reporting one or more of their posts will also add them to the blacklist.
 
What you entered was just adding that to the normal watchlist as if it were a regular expression. Note that the full URL is needed, because user names are not unique across all SE sites.
@AdrianMole Yes, in that case, as @cigien notes: !!/allspam <user URL>
 
@Jesse @Makyen
 
7:22 PM
Did we ping @AdrianMole enough times, I wonder?
 
I gave their second one the canned "spam warning" comment. But both are very recent posts (a few minutes apart).
@CodyGray No.
(My last 2 reports in SOBotics, if you're interested.)
 
[ SmokeDetector | MS ] Manually reported answer (batch report: post 1 out of 2) (94): Service ID invalid when trying to use EmailJS with React by Anurag Vaibhav on stackoverflow.com
[ SmokeDetector | MS ] Manually reported answer (batch report: post 2 out of 2) (94): emailjs with react-hook-form's handleSubmit function is not sending email by Anurag Vaibhav on stackoverflow.com
 
sdc watch emailjs\.blogspot
 
7:24 PM
@cigien The pattern is a blogspot watch but keeps the TLD, in most cases this should be removed. Append -force to the command if you really want to add this pattern.
 
Ooh, nice :)
 
Haha, I guess that got snuck in while MS was down :-)
 
Hmm, almost a month ago actually. I must have missed that, or forgotten.
 
!!/whois admin
 
7:27 PM
@rene I am aware of 8 admins. Currently in this room: Makyen, ArtOfCode. Not currently in this room: Thomas Ward, angussidney, tripleee, thesecretmaster, Andy, Undo.
 
@Jesse There's also a list of commands which includes that query.
 
@Jesse ^^
let's ping Jesse a few times ...
 
Sounds good.
 
A ping-fest to distract from the spam-attack?
 
[ SmokeDetector | MS ] Potentially bad keyword in answer, toxic answer detected (80): Python Crash Course project: Object has no attribute by Ralf J Egger on stackoverflow.com
 
As far as I'm aware, all of the new metasmoke accounts have already been handled/activated. Activating could easily have happened between when the notice about needing activation on metasmoke was shown to a new user immediately after signing up and when they end up here in CHQ asking for activation. The user would need to reload the metasmoke page after the Flagger role has been added, but the instructions say to come in here to ask for activation.
In other words, if I see the new metasmoke user message in here, I'll normally check on it. That doesn't always happen, but it happens if I see it.
Prior to forwarding a ping, please use the "metasmoke user" link in the "New metasmoke user <> created" message to double-check to see if the user has already been given the "Flagger" role. Note that link is a search of users by name, so may return more users in the list than just the new user. The new user will likely be at the bottom of the list, as it's sorted by increasing metasmoke userID.
If the user already has the "Flagger" role, then please politely ask them to reload the metasmoke page.
@Jesse This has been done. :)
 
I did check for the ping I sent, though it's possible it happened right after I sent a ping. All the same, thanks Makyen :)
 
@Spevacus Thank you :)
 
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): Python: Store all received values in a different string with threads by iBud on stackoverflow.com
 
7:43 PM
@Spevacus Yep. Thanks for the ping. That one had not been done. The pings aren't bad/wrong, it's just in some cases it could be better. :;
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Vectorized backtesting using a Pandas Dataframe with stop loss and take profit by CeBoLaRk on stackoverflow.com
[ SmokeDetector | MS ] Link at beginning of answer (34): Intuitive Understanding of the constant "$e$" by El Vaf on math.SE
 
!!/unwatch 217543
!!/watch 217543
 
@Makyen No such command 'unwatch-number'.
 
@Makyen Watched as a number, but can't be detected by the numbers detection, due to being too short.
 
7:48 PM
[ SmokeDetector ] Blacklists reloaded at rev 44ba3b83b (SmokeDetector: Auto watch of 217543 by Makyen) (running on teward/Osiris)
[ SmokeDetector ] Blacklists reloaded at rev c9cfdd627 (SmokeDetector: Auto unwatch of 217543 by Makyen) (running on teward/Osiris)
[ SmokeDetector ] Blacklists reloaded at rev 6eafc7dba (SmokeDetector: Auto unwatch of 217543 by Makyen) (running on teward/Osiris)
[ SmokeDetector ] Blacklists reloaded at rev d50ac4e1b (SmokeDetector: Auto watch of 217543 by Makyen) (running on teward/Osiris)
 
[ SmokeDetector ] GitHub Action workflow build (3.9): failure on 44ba3b8 by SmokeDetector in the master branch
 
[ SmokeDetector | MS ] Link at beginning of answer (34): Understanding the "Birthday Problem" by El Vaf on math.SE
 
[ SmokeDetector ] GitHub Action workflow build (3.6): failure on 44ba3b8 by SmokeDetector in the master branch
 
8:01 PM
[ SmokeDetector | MS ] Link at beginning of body, potentially bad keyword in body (42): Is there a way to convert thinkscript's CompoundValue function into tradingview's PineScript? by jack h on stackoverflow.com
 
[ SmokeDetector | MS ] Link at beginning of answer, pattern-matching website in answer (111): Are there any good Stack Exchange sites for daily life questions? by Sana on meta.SE (@Ollie)
 
@metasmoke Yes, I know. Failures fixed in the sequence of watches and unwatches.
 
sdc watch anzalweb\.ir
 
9:01 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Companions in Novigrad's Arena? by PC William on gaming.SE
 
GitHub is down currently (throwing 500 errors on any URL) - I'm curious if we'll have problems with our watch commands.
 
9:16 PM
fp- feedback received on [MS] Companions in Novigrad's Arena?
 
[ SmokeDetector | MS ] Manually reported answer (94): Can you be afraid if you're dead? by user147256 on rpg.SE
 
tpu- feedback received on [MS] Can you be afraid if you're dead?
 
9:22 PM
@Spevacus It will impact being able to do any watch or blacklist commands, with the possible exception of commands which are completely based on the GitHub API, if the GitHub API is not experiencing the same issues.
 
[ SmokeDetector | MS ] Few unique characters in answer, mostly punctuation marks in answer (123): Uncaught TypeError: Cannot read properties of undefined (reading 'x') by cat on stackoverflow.com
 
@SmokeDetector naa-
 
@SmokeDetector tpu-
 
@SmokeDetector While I did just delete this, rather than R/A delete it (and definitely not R/A delete, given the grace period edit), "Lmao" is rude as an answer from the point of view of the person who asked the question. How does it feel, from the point of view of the person who asked, to get an answer of "LMAO", without any other context?
 
9:40 PM
[ SmokeDetector | MS ] Bad keyword with email in answer (85): The book "Pro Javascript Design Patterns" - is it a bad idea? by mdajobs on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Export DataGrid to PDF using c# by DotNet Developer on stackoverflow.com
 
10:09 PM
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, obfuscated word in body, obfuscated word in title, +3 more (389): C0inBasE_ 😠– l-804–454–8895 $N0V$ ☎️ "SUpp0rt Number $N0V$ C0inBasE_ PhOnE NuMber by dbwgmljcyulr on stackoverflow.com
[ SmokeDetector | MS ] Shortened url in body (46): Problema con canvas en la inclusión de foto y QR en carnet by Luis Gonzalez on es.stackoverflow.com
 
11:07 PM
[ SmokeDetector | MS ] Bad keyword in body (95): Which test to use in "Ordinal x Categorical" Data by Silefil on stats.SE
 
!!/watch- premier-kora\.com
 
teward/Osiris: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 483eb8b0b (SmokeDetector: Auto watch of premier-kora\.com by Makyen) (running on teward/Osiris, Python 3.8.10)
Restart: API quota is 15134.
CI on 0240152 succeeded.
 
11:15 PM
[ SmokeDetector ] GitHub Actions: success on 0240152 by makyen in the master branch
 
[ SmokeDetector ] SmokeDetector started at rev 0240152ce (Makyen: Number watch and blacklist normalization) (running on teward/Osiris, Python 3.8.10)
Restart: API quota is 15033.
 
11:50 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Average EC2 Uptime? by embarassinglybadpython on stackoverflow.com
Makyen/EC2-linux: Executing automatic scheduled reboot.
 
00:00 - 16:0016:00 - 00:00

« first day (2932 days earlier)      last day (881 days later) »