« first day (4013 days earlier)      last day (32 days later) » 

00:00
@Makyen I should have addressed this, and still need to, but I don't think syncing my fork (the thing I did) should mess with the main SD branch, right...? I was also surprised by the message, but considering this, I don't think it affected the main SD repo
> This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
@cocomac Nope. Not a problem. It's all good on your side. It's a bug in what was reported by MS into chat. The link to the branch should have been to the master branch in your fork, not to the main repository.
[ SmokeDetector ] SmokeDetector started at rev 61ae107dd9 (Makyen: Use 10 workers instead of 20 for blacklist DNS testing) (running on teward/Cerberus, Python 3.10.12)
[ SmokeDetector ] GitHub Actions: success on 61ae107 by makyen in the master branch
00:04
Restart: API quota is 90827.
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body (2): RPZ Not blocking sites in Bind9 ✏️‭ by Daniel Severn‭ on serverfault.com
Google's public DNS page mentions a 1500 query-per-second limit, which seems higher than what we would hit, but if we're pooled with other GitHub runners/IP's,maybe?
00:26
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (269): How to get refund back from wrong recharge Jio?‭ by alwstzar‭ on salesforce.SE
00:36
[ SmokeDetector | MS ] Bad keyword with email in answer, bad phone number in answer, email in answer, pattern-matching email in answer, potentially bad keyword in answer, +1 more (437): Does a caster need a free hand to cast a spell from a spell scroll?‭ by deas vearest‭ on rpg.SE
@JeffSchaller It's possible, but the NS validation test, which does the most DNS requests, is usually the same one that takes the longest. In fact, that test is specifically separated out into its own thread, because it takes the most wall clock time. My note in the code from when I set that up is that it was taking about 105 seconds to run the test. There are, currently, on the order of 5k entries.
It's possible that we're also doing a lot more DNS requests than I thought from the findspam tests, as those are some of the ones that are commonly failing, and would be running concurrently with both other findspam tests and the NS validation tests.
!!/watch- dronihaspell(?:@yahoo\.com)?
@cocomac I think I'll do a separate PR, as while related, it is a different issue.
[ SmokeDetector | MS ] Manually reported question (93): ng looking for a fullstack or backend positon‭ by Danny Zhao‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title (196): Jio wrong recharge complaint number -‭ by Raju sahu‭ on gis.SE
01:02
!!/location
Hello
[ SmokeDetector | MS ] Bad phone number in body, potentially bad keyword in title (101): Jio wrong recharge complaint number -‭ by Radhika man‭ on salesforce.SE
[ SmokeDetector | MS ] Bad phone number in answer, blacklisted user (173): Jio wrong recharge complaint number -‭ by Radhika man‭ on salesforce.SE
tpu- feedback received on [MS] Jio wrong recharge complaint number -‭
PR#13797 ("Support short multiline messages") opened by CoconutMacaroon
[ SmokeDetector ] GitHub Actions: success on ada0480 by CoconutMacaroon in the fix-short-multiline branch
01:26
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): Реферальный код MEXC BET999 — зарегистрируйтесь в MEXC в 2024 году‭ by chaucryoto‭ on askubuntu.com
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body (48): Ciputra University Surabaya Entrepreneur Campus‭ by UC Cyber‭ on academia.SE
[ SmokeDetector | MS ] Potentially bad keyword in title (1): Are claims that Jews did wtc increasing?‭ by R Dd‭ on skeptics.SE
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): What is Digital marketing?‭ by Dabarlal chivade‭ on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title (194): Реферальный код Bitget: bet168 — зачем использовать реферальный код Bitget?‭ by chaucryoto‭ on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title (194): What is Digital marketing? ✏️‭ by Dabarlal chivade‭ on askubuntu.com
tpu- feedback received on [MS] What is Digital marketing?‭
tp feedback received on [MS] What is Digital marketing?‭
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (267): MEXC Referral Code BET999 - Register with MEXC in 2024 ✏️‭ by chaucryoto‭ on askubuntu.com
01:40
API quota rolled over with 90404 requests remaining. Current quota: 99999.
stackoverflow: 2844
math: 1241
physics: 332
superuser: 277
electronics: 265
mathoverflow.net: 237
stats: 219
ru.stackoverflow: 218
askubuntu: 215
tex: 177
diy: 145
unix: 143
gis: 110
blender: 108
philosophy: 101
scifi: 97
hermeneutics: 97
serverfault: 92
es.stackoverflow: 81
english: 76
salesforce: 76
ell: 75
mathematica: 73
dba: 72
apple: 68
codegolf: 63
judaism: 56
politics: 55
travel: 51
japanese: 50
ethereum: 48
sitecore: 47
datascience: 44
law: 43
mechanics: 40
codereview: 40
puzzling: 40
academia: 39
[ SmokeDetector | MS ] Potentially bad keyword in answer, username similar to website in answer, blacklisted user (147): How to create a condition that differentiates string and number‭ by FQR Host‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title (194): What is Digital Marketing?‭ by Dabarlal chivade‭ on serverfault.com
tpu- feedback received on [MS] What is Digital Marketing?‭
01:58
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Act/365 (Canadian Bond) day count convention‭ by ggill‭ on quant.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How can I change my code to make a flare launch from a gun?‭ by edfawef waef‭ on stackoverflow.com
[ SmokeDetector | MS ] Offensive answer detected, toxic answer detected (159): Who is the daughter of women? Daniel 11:17‭ by Jennifer Augustine‭ on hermeneutics.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): Robot localization (IMU + GPS) position Without GPS‭ by jones2126‭ on robotics.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): VSCode Integrated Terminal does not work in elementary OS Juno ✏️‭ by RicaBenhossi‭ on elementaryos.SE
[ SmokeDetector | MS ] Bad phone number in answer (100): Jio wrong recharge complaint number -‭ by Crvfv‭ on salesforce.SE
02:18
hmm
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Can I get a refund from Jeevansathi‭ by Hfvuhf Ku‭ on gis.SE
@JeffSchaller want to proofread my regex before i create a watch?
!!/blacklist-number- 9244820361(?#NO NorAm)
02:22
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (74): Cellphone-obsessed friend (and driver) ✏️‭ by Spotify Ak‭ on interpersonal.SE
A J
A J
@SmokeDetector tpu-
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
02:55
@Dragonrage 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 924-482-0361 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 !!/blacklist-number 924-482-0361. Append -force to the command word(s) if you really want to add the pattern you provided.
good catch. didnt realize the watch didnt go through
@Dragonrage Well, I thought I'd be reasonably stealthy and just edit this, but I failed my stealth roll. :)
lol
do you mind reviewing a watch real quick? not sure if i got the bookending correct
^jio[\W_]*+wrong[\W_]*+recharge[\W_]*+complaint[\W_]*+number[\W_]*+$
Yeah, I happened to load the GitHub commits page and didn't see it, so took a closer look. I didn't notice the wrong command prefix. That's probably something we should have SD look for and reply to with a "I didn't understand that".
03:00
apparently me editing the message reverted the fix on the command. weird
@Dragonrage I'm unsure of the value of the end [\W_]*+$, unless you're concerned about extra "_" characters preventing a match.
i blame caching
That's probably it.
@Makyen wasnt sure if it would match if there was a space at the end or not. i havent used bookends too frequently, so am a bit unfamiliar with how they work
i just noticed there were multiple instances of the same title, and figured it would be a useful watch
@Dragonrage Without the [\W_]*+$, it will match with any character after it which is not [A-Za-z0-9_], or no characters after it.
03:05
@Makyen hmm, yeah you might be right. probably dont need to worry about FPs for that. would be fairly unlikely
@Dragonrage Looking at it again, I probably wouldn't have the ^ at the beginning, unless you really want to limit it to just titles, but I don't see a reason to do that.
Yeah, FP on just the words, even outside of titles, would be quite unlikely.
!!/watch jio[\W_]*+wrong[\W_]*+recharge[\W_]*+complaint[\W_]*+number
@Dragonrage 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.
!!/bisect Jio wrong recharge complaint number
03:10
@Dragonrage Matched by wrong[\W_]*+recharge on line 68244 of watched_keywords.txt
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title (194): PhonePe Wrong Transaction Refund Payment - Developer Community Forum‭ by Jaanu Jaan‭ on webapps.SE
!!/blacklist-number- 0930-2833-823
@SmokeDetector @Makyen do you know why this watch didnt catch the titles for these posts?
!!/unwatch- wrong[\W_]*+recharge[\W_]*+from
!!/test Jio wrong recharge complaint number
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 4-18: wrong recharge
Potentially bad keyword in title - Position 4-18: wrong recharge
Potentially bad keyword in username - Position 4-18: wrong recharge
!!/test Jio wrong recharge complaint number
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 4-18: wrong recharge
Potentially bad keyword in title - Position 4-18: wrong recharge
Potentially bad keyword in username - Position 4-18: wrong recharge
@Dragonrage After a bit of investigation, I'm unsure why it wasn't detected.
03:22
@Makyen chalk it up as another one of life's unsolved mysteries
Yeah, but it's concerning.
yeah. maybe the two similar watches were breaking it?
That shouldn't do it, but ... maybe?
could theoretically rewatch it and test?
We'd probably need them to be in the same order, so reverting the commit would be the way to go.
But, they worked together on other posts, so there's going to be more to it. For example, metasmoke.erwaysoftware.com/post/508004 (worked), which was less than a minute prior to metasmoke.erwaysoftware.com/post/508005 (failed).
03:29
@Makyen the second is an answer though, right?
would that cause the title detection to be run?
Sigh, right, that's the answer for both of the ones which were not detected.
ah, i see
i too did not catch that
@Makyen My derogatory comment was directed at myself, but I realized it could be misunderstood; basically a slapping myself on the forehead moment.
eg. facepalm
03:42
@Dragonrage Yep. :)
@cocomac Sorry for not responding. I got distracted and lost this ping. Yes, a separate PR would be best, as you've done. Thanks.
Is this issue still unresolved? I feel like I've seen "username similar to url" a couple times before.
Oh wait I just can't read. Never mind.
04:34
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started in standby mode at rev 186c8475d0 (SmokeDetector: Auto watch of simbye\.com by VLAZ) (running on Makyen/EC2-linux)
[ SmokeDetector | MS ] Bad keyword in answer, pattern-matching website in answer, potentially bad keyword in answer, +1 more (240): Issues with Phone Authentication in Ionic/Angular with Capacitor on iOS using @capacitor-firebase/authentication and @angular/fire‭ by VirtueNetz‭ on stackoverflow.com
!!/watch- virtuenetz(?!\.pk)
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title, blacklisted user (272): Achieve High-Quality Business Contacts in China with Ready Mailing Team’s Email List‭ by rabeya bosri‭ on superuser.com
[ SmokeDetector | MS ] Mostly non-latin answer (51): HTML time tag for duration‭ by Yohan Perera‭ on stackoverflow.com
tpu- feedback received on [MS] HTML time tag for duration‭
[ SmokeDetector | MS ] Username similar to website in answer (73): How can I secure use of fopen on a CSV file?‭ by True Criminal Stories‭ on stackoverflow.com
Cow
Cow
sdc watch truecriminalstories\.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Looking for GPT prompt management tools‭ by Jan Stepkovich‭ on softwarerecs.SE
05:21
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Makefile Errors When Migrating from Old SDK to Vitis 2020.2 on a Custom Zynq-7000 Board‭ by David HOU‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad phone number in body, potentially bad keyword in body, potentially bad keyword in title (102): How can if I refund my Airtel wrong recharge?‭ by Kamal Shek‭ on gis.SE
05:40
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad keyword in answer (2): Are there any ways of preventing hereditary hair loss in people who have NOT YET shown signs of loss?‭ by maneadvancedhair‭ on medicalsciences.SE
Cow
Cow
@SmokeDetector user has two almost identical answers now
@SmokeDetector user is 100% representing maneadvancedhair.com
[ SmokeDetector | MS ] Link at end of answer, potentially bad ip for hostname in answer (64): Application must hold android.permission.REQUEST_COMPANION_PROFILE_AUTOMOTIVE_PROJECTION connecting to DHU‭ by Zeng Bo‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad phone number in body, potentially bad keyword in body (101): what is the cheapest day of the week to buy amtrak tickets?‭ by Suresh Kumar‭ on superuser.com
Cow
Cow
sdc blacklist-keyword cheapest[\W_]*+day[\W_]*+of[\W_]*+the[\W_]*+week
Cow
Cow
no hits on SE
06:02
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Dynamic content based on a URL parameter‭ by Bruno Miranda‭ on wordpress.SE
teward/Cerberus: Executing automatic scheduled reboot.
Restart: API quota is 98857.
Cow
Cow
sdc watch refund[\W_]*+contact[\W_]*+customer[\W_]*+support
no hits on SE
Cow
Cow
currently 3:0:0
@Cow While this is, probably, OK, for now, please keep in mind that the posts on MS are very heavily weighted towards TP. In particular, please take care with potential entries that could reasonably be used in legitimate posts. For example, that phase could easily show up in a question or answer. For example, this answer comes very close.
Cow
Cow
06:12
all right
sdc unblacklist cheapest[\W_]*+day[\W_]*+of[\W_]*+the[\W_]*+week
Cow
Cow
sdc watch cheapest[\W_]*+day[\W_]*+of[\W_]*+the[\W_]*+week
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): What is the Lagosec Inc Charge?‭ by WebRanky‭ on meta.SE
Cow
Cow
@Makyen what about this one: call[\W_]*+[\w]+[\W_]*+customer[\W_]*+care I cannot search it on SE, I tried a few like Airtel and Jio and they did not have any hits. Would it be ok to watch? Currently 68:2:0 - the two fps are 8 years old
tpu- feedback received on [MS] What is the Lagosec Inc Charge?‭
06:16
@Cow I'm much more comfortable with that, but changing it wasn't necessary. The counter-argument in favor of having it as a blacklist entry is that it's a phase that's actively in use by a spammer, multiple times within the last month.
!!/watch- cardvcc\.com
Cow
Cow
@Makyen did you just counter argue your own comment? :D
I'm confused now
@Cow You could try it and see how it goes. However, I'd expect that to show up on SE, but perhaps not that much, as "customer care" doesn't show up all that often compared to "customer service".
Cow
Cow
yeah that's the result I came up with also
but all this is still new to me, so I'm just trying the best I can
06:20
@Cow Yes. I was trying to present both sides. As I stated, it's probably OK to have that one on the blacklist.
Cow
Cow
sdc watch call[\W_]*+[\w]+[\W_]*+customer[\W_]*+care
@Cow Yep. There's a steep learning curve. You're doing well.
Cow
Cow
It's also why I try to document it, so that it's on record
Cow
Cow
06:22
sdc unwatch cheapest[\W_]*+day[\W_]*+of[\W_]*+the[\W_]*+week
Cow
Cow
sdc blacklist-keyword cheapest[\W_]*+day[\W_]*+of[\W_]*+the[\W_]*+week
let's try it as blacklist
sdc watch- vifreehd\.com
06:25
[ SmokeDetector ] Blacklists reloaded at rev ebd853e76e (SmokeDetector: Auto watch of vifreehd\.com by VLAZ) (running on teward/Cerberus)
@VLAZ from this spam. It was a reply I didn't see until later
sdc watch- (?-i:hubunganindonesia)(?# t.ly)
sdc watch- AT777
@VLAZ with the two watches before it - from Discussion spam
[ SmokeDetector ] Blacklists reloaded at rev 6d57db42a6 (SmokeDetector: Auto watch of AT777 by VLAZ) (running on teward/Cerberus)
06:37
[ SmokeDetector | MS ] Bad ip for hostname in answer, bad ns for domain in answer, bad keyword in answer, blacklisted username, blacklisted website in answer (455): Windows (10 and Server 2019): Why suddenly Search Active Directory button is greyed out (disabled)?‭ by Bhanukumar‭ on superuser.com
[ SmokeDetector | MS ] Bad ip for hostname in answer, bad ns for domain in answer, bad keyword in answer, blacklisted username, blacklisted website in answer, +1 more (518): Windows (10 and Server 2019): Why suddenly Search Active Directory button is greyed out (disabled)? ✏️‭ by Bhanukumar‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): What is upcoming scope of digital marketing in india?‭ by mital kadam‭ on stackoverflow.com
[ SmokeDetector | MS ] Offensive title detected, potentially bad keyword in title (57): fu*k you xflock4!‭ by user598575‭ on unix.SE
Cow
Cow
@SmokeDetector why would you make a title like that
06:49
Offensive title detected - Position 0-8: fu*k you
Potentially bad keyword in title - Position 0-5: fu*k
Cow
Cow
sigh
I suppose the poster finds xflock4 very attractive.
Cow
Cow
haha
HAHAHA
[ SmokeDetector | MS ] Blacklisted user (73): bot in python for irc chat using proxy‭ by khushnuma‭ on stackoverflow.com
naa- feedback received on [MS] bot in python for irc chat using proxy‭
fp- feedback received on [MS] fu*k you xflock4!‭
Cow
Cow
06:54
@SmokeDetector someone came in clutch
funny comment by user though
my question was: xflock 4 doesnt work ! but the website didn't let me enter it, I'm sorry! — user598575 8 mins ago
Cow
Cow
hehe
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad keyword in answer (2): how can a buyer and vendor can video chat with each other‭ by myAcademiazone‭ on magento.SE
07:13
[ SmokeDetector | MS ] Bad ns for domain in answer, bad keyword in answer, blacklisted website in answer, pattern-matching website in answer, potentially bad ip for hostname in answer, +1 more (420): Can a large hole be reliably drilled in a table _by hand_?‭ by official‭ on diy.SE
Cow
Cow
07:30
Could you imagine... haha
[ SmokeDetector | MS ] Bad keyword in answer, link at end of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (154): How to stop API execution without a loop activity in the source code using c# API‭ by desi asmara‭ on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted user (73): what should be my name in research article?‭ by Jack Smith‭ on academia.SE
Cow
Cow
@SmokeDetector Buy crystal Meth online
sdc watch (?-i:3YZmu99)(?# bit.ly)
[ SmokeDetector | MS ] Blacklisted website in body, link at end of body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (199): Unleash Your Lean Potential with Nagano Tonic‭ by RosemaryReid12‭ on meta.SE
[ SmokeDetector | MS ] Bad keyword in link text in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (85): Block Comments in Clojure‭ by beauti queen‭ on stackoverflow.com
tpu- feedback received on [MS] Block Comments in Clojure‭
@SmokeDetector tpu-
Cow
Cow
07:57
sdc watch callgirlsinraipur\.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, potentially bad keyword in body (293): How to refund a wrong transaction in Paytm‭ by Jama Das‭ on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in answer, bad phone number in answer, potentially bad keyword in answer (190): How to refund a wrong transaction in Paytm‭ by Jama Das‭ on askubuntu.com
08:18
[ SmokeDetector | MS ] Bad phone number in body, potentially bad keyword in body, potentially bad keyword in title (102): Jio wrong recharge complaint number-‭ by jinny‭ on askubuntu.com
[ SmokeDetector | MS ] Bad phone number in answer, potentially bad keyword in answer (101): Jio wrong recharge complaint number-‭ by jinny‭ on askubuntu.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): Sonoma problem: no longer able to use vnc through tunnel on private network‭ by Thomas Scott‭ on apple.SE
sdc watch- amansamrat\.com
sdc watch-number- +91-7814557515
@VLAZ with the watch - from Discussion spam
08:30
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on 7b1a240 by SmokeDetector in the master branch
[ SmokeDetector ] GitHub Action workflow build (3.8): failure on 16b2c3a by SmokeDetector in the master branch
08:43
tpu- feedback received on [MS] Jio wrong recharge complaint number-‭
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
tpu- feedback received on [MS] Jio wrong recharge complaint number-‭
[ SmokeDetector | MS ] Bad keyword in link text in answer, link at beginning of answer, potentially bad keyword in answer, username similar to website in answer (195): Assistance Required for Identifying Persistent Android Auto Device Identifiers Across Connections‭ by Coupon Reals‭ on stackoverflow.com
Cow
Cow
sdc watch couponreals\.com
[ SmokeDetector ] Blacklists reloaded at rev c691c2deda (SmokeDetector: Auto watch of couponreals\.com by Cow) (running on teward/Cerberus)
[ SmokeDetector | MS ] Potentially bad keyword in answer, potentially problematic ns configuration in answer (2): Transform Travel Table - SQL‭ by JYOTIKA KUSHWAHA‭ on stackoverflow.com
Cow
Cow
sdc watch coupon[\W_]*+reals(?!\.com(?<=couponreals\.com))
Cow
Cow
sdc watch trekos\.in
@Cow 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.
Cow
Cow
doh
or
moh
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): What is "Hotel Mode" on a turboprop engine?‭ by Ahmad Dan-Hamidu‭ on aviation.SE
[ SmokeDetector ] GitHub Action workflow build (3.12): failure on c691c2d by SmokeDetector in the master branch
09:06
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): AWS CloudShell Error 'Unable to start the environment...' ✏️‭ by a deleted user on stackoverflow.com
[ SmokeDetector | MS ] Bad ip for hostname in answer, bad ns for domain in answer, bad keyword in answer, blacklisted website in answer, potentially bad keyword in username (366): Is NATO a purely defensive organisation, ruling out attacks from NATO?‭ by spammer‭ on politics.SE
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ip for hostname in body (99): Memory Error in Code Execution on System with HPE P11444-691 Memory Module‭ by Dan Griffin‭ on stackoverflow.com
Cow
Cow
@SmokeDetector the usual direct link to their webshop
09:35
[ SmokeDetector | MS ] Bad keyword with email in answer (85): How to keep IMAP access to gmail after May 30? ✏️‭ by Stancho‭ on superuser.com
[ 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, +2 more (462): How can a logistics course help in developing skills for a global career?‭ by Transglobe seo‭ on superuser.com
[ SmokeDetector | MS ] Bad keyword with email in body, pattern-matching email in body (137): A way to recover scammed Bitcoin investment‭ by Peyton Parrish‭ on bitcoin.SE
[ SmokeDetector | MS ] Bad keyword in link text in body, potentially bad keyword in body, potentially bad keyword in title (76): Top 5 Benefits of Choosing Scalp Micropigmentation in Delhi‭ by pratima bhutani‭ on meta.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Instagram opens the main page of the site instead of the link‭ by Sam‭ on stackoverflow.com
Cow
Cow
sdc watch financeinvestmentlegalteam(?:@gmail\.com)?
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title (194): Manasa Defence Academy stands as one of the most reputable institutions in India‭ by Raj kumar‭ on stackoverflow.com
Cow
Cow
jesus christ, my boss just got fired
09:57
Didn't know you work directly for Him
Cow
Cow
heh, well I guess normally I wouldn't care, but this guy is really nice
I just hope I dont get the boot
if is_cow():
    fire = False

« first day (4013 days earlier)      last day (32 days later) »