« first day (2393 days earlier)      last day (1427 days later) » 
00:00 - 16:0016:00 - 00:00

4:03 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): ErrorException Trying to get property 'created_at' of non-object by raj kumar on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Wordpress Child-Theme CSS not Reflecting on Site by CbshopIn Coupons on stackoverflow.com
fp- feedback received
tp feedback received on Remote SASL in Apache Kafka [MS]
tp feedback received on Remote SASL in Apache Kafka [MS]
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body (2): The crypto speed issue by Mr. Freewallet on ethereum.SE
fp- feedback received
tp feedback received on About an adjective "lurid" [MS]
[ SmokeDetector | MS ] Potentially bad keyword in username (1): Problem in nginx server not running php files suddenly ✏️ by Devman1 on stackoverflow.com
 
4:22 PM
@SmokeDetector fpu-
 
@SmokeDetector fpu-
 
[ SmokeDetector | MS ] Luncheon meat detected (40): when i upload an media, then the save button does not clickable by white black on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How would I remove certain roles from all members in a guild that have it? by Diamond on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in body, repeating characters in body (167): Getting two highest marks from lists ✏️ by JJJ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, repeating characters in body, repeating characters in title (397): aaaaaaaaaaaaaaaaaaaaaaaddddddddddd ✏️ by JJJ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, potentially bad keyword in body, potentially bad keyword in title, repeating characters in body, +1 more (332): ddddddddddddddddd ✏️ by JJJ on stackoverflow.com
[ SmokeDetector | MS ] Pattern-matching website in body (97): Google Page Speed by Bhargav Joshi on wordpress.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Multi-instance tomcat server.xml permission denied ✏️ by Nick on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Why does selenium scriptwork only sometimes? by codedo on stackoverflow.com
tp- feedback received on aaaaaaaaaaaaaaaaaaaaaaaddddddddddd [MS]
tp- feedback received on ddddddddddddddddd [MS]
fp- feedback received on Google Page Speed [MS]
tp- feedback received on Getting two highest marks from lists [MS]
[ SmokeDetector | MS ] Potentially bad keyword in body (1): excel get max value for each day with corresponding time by Matteo Cunzolo on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how to use barryvdh/laravel-snappy package in live server cpanel by Abdul Bazith on stackoverflow.com
 
5:12 PM
!!/approve 3937
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Stochastic gradient descent for a function of multiple variables? by Str91 on math.SE
teward/Osiris: Executing automatic scheduled reboot.
Restart: API quota is 12739.
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): How to prevent adding the same student's ID or numeric order in ListView? by Đức Thắng on stackoverflow.com
 
5:32 PM
[ SmokeDetector | MS ] Potentially bad keyword in title (1): Where to buy a 6502 chip by Bigmalc40 on retrocomputing.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Securing my Firebase account by Dennis.Moo on security.SE
iBug/Sandy: Executing automatic scheduled reboot.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How would I remove certain roles from all members in a guild that have it? by Diamond on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): excel get max value for each day with corresponding time ✏️ by Matteo on stackoverflow.com
fp- feedback received on Securing my Firebase account [MS]
fp- feedback received on Where to buy a 6502 chip [MS]
 
6:08 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Thunderbolt 3 second computer processor sharing by Tristram Tolliday on superuser.com
 
6:35 PM
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): How to keep connections alive on ssh MacOS Catalina? by Khalid Ayaz Khan on apple.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Limit cosine series by Akanksha Bhardwaj on math.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, username similar to website in answer (63): Flutter custom Google Map marker info window ✏️ by Abhishek Duhoon on stackoverflow.com
fp- feedback received on Limit cosine series [MS]
fp- feedback received
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer (2): Restarting explorer.exe only opens an explorer window ✏️ by Alex on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): What should I learn first to be a coder? by Nadim on stackoverflow.com
fp- feedback received
[ SmokeDetector | MS ] Bad keyword in answer, link at end of answer, potentially bad keyword in answer, username similar to website in answer (209): Bet365 website is not working by gilaliga on stackoverflow.com
tpu- feedback received
 
7:01 PM
!!/watch gilaliga(\.com)?
 
!!/test gilaliga
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 0-8: gilaliga
Potentially bad keyword in title - Position 0-8: gilaliga
Potentially bad keyword in username - Position 0-8: gilaliga
 
!!/test gilaliga.com
 
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 0-12: gilaliga.com
Potentially bad keyword in title - Position 0-12: gilaliga.com
Potentially bad keyword in username - Position 0-12: gilaliga.com
fp- feedback received
[ SmokeDetector | MS ] Few unique characters in answer, mostly punctuation marks in answer, repeating characters in answer (203): Rigify Error Bone cannot connect chain bone by Fede Dominguez on blender.SE
naa- feedback received
 
7:22 PM
@NobodyNada In general, when you're wanting to watch text which is also used as a domain name, it's preferable to use two watchlist entries, rather than one. One entry for the domain (e.g. gilaliga\.com) and one for the text, with the domain excluded (e.g. gilaliga(?!\.com)). The reason for having two is that, assuming they keep showing up in spam, they will eventually be moved to the blacklists, which are separated into the keyword blacklist and website blacklist.
If there are separate entries in the watchlist, it's trivial to blacklist one with just a !!/blacklist-* command, while, perhaps, the other doesn't yet qualify for the blacklist. If there's only one entry in the watchlist, then whoever is moving one or both to the blacklist has to either edit the watchlist to only be the one not being moved to the blacklist, or if moving both, manually !!/unwatch the entry that covers both.
From what I've seen, it is both easier in the long run to start with separate watches for the text and domain, and reduces the likelihood that we end up with an entry in the watchlist that causes a double-detection, because it didn't get manually cleaned up when either the text or domain are moved to the blacklist. I know that not optimizing the regex you're adding feels wrong/strange, but it does appear to help in maintaining the lists.
 
@Makyen Sounds sensible; thank you!
!!/unwatch gilaliga(\.com)?
 
!!/watch gilaliga\.com
 
!!/watch gilaliga(?!\.com)
 
7:25 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Creating Git post-receive hook to post Tag name by Leonid Eletskikh on stackoverflow.com
fp- feedback received
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Shopify Private App Configuration returning oauth error by sahanda on stackoverflow.com
fp- feedback received
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): MySQL Workbench not working in Ubuntu 20.04 by Jfrd on askubuntu.com
fp- feedback received
 
7:41 PM
@NobodyNada np. Thanks for taking care of it.
 
7:53 PM
[ SmokeDetector | MS ] Pattern-matching website in body (97): Google Page Speed by Bhargav Joshi on wordpress.SE
fp feedback received
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Slow boot time Ubuntu / Linux Mint 19.3 by Steve J on askubuntu.com
fp- feedback received
 
@SmokeDetector f
@SmokeDetector f
@SmokeDetector naa-
 
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): calculate total price of product for different attribute by Bikash Waiba on magento.SE
fp- feedback received
[ SmokeDetector | MS ] Few unique characters in body (94): Вопрос про вопрос Вопрос про вопрос by newuser on ru.stackoverflow.com
 
8:12 PM
@SmokeDetector Google Translate: "Question about question. Question about question. Question about question."
Not quite R/A I guess, but pretty close
 
fp- feedback received
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Is it possible to remove thumbnail of post on main page? by Denise Hilton on stackoverflow.com
 
@SmokeDetector Pretty fishy, though I don't see any direct evidence of affiliation
 
@NobodyNada probably voting fraud. Two non-answers were posted, accepted and upvoted. Question has been removed now.
 
@Glorfindel Ooh, good catch
 
It was actually pretty funny to watch (with my limited understanding of Russian).
 
8:25 PM
@SmokeDetector k
 
8:37 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Add a char at the beginning of a pointer to char in C ✏️ by Chriss on stackoverflow.com
fp- feedback received
fp- feedback received
[ SmokeDetector | MS ] Pattern-matching website in body, potentially bad keyword in body (98): where to order weed online i found some but unsure array example I found online by tommyhook on stackoverflow.com
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad keyword in body (294): Inhale fresh and clean air with Safebreath Pro Mask by breathsfe on meta.SE
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title (194): How to download Lucky Patcher Without any error? and which device is in work by thomer likena on stackoverflow.com
fp- feedback received
 
9:07 PM
@SmokeDetector k User links to website in their profile
 
9:31 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Who first played Moonlight Sonata on electric guitar? by Arunabh Bhattacharya on musicfans.SE
[ SmokeDetector | MS ] Few unique characters in body (94): Hurricane Electric IPV6 tunnel, TLS handshake issue ✏️ by MevatlaveKraspek on superuser.com
tp- feedback received
 
9:50 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Xboard 4.9 installation by Protágoras on chess.SE
fp- feedback received
[ SmokeDetector | MS ] Few unique characters in answer, repeating words in answer (172): How do you compare Ubuntu Server to Snappy Ubuntu Core? by lolll on askubuntu.com
tpu- feedback received
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Cannot find insider transaction on chart by user2356580 on money.SE
[ SmokeDetector | MS ] Bad keyword with email in answer, pattern-matching email in answer (184): Can someone take money out of my account with just my Account & Routing number? by jeffrey cage on security.SE
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Why didn't Dumbledore let Harry die in Order of the Phoenix? ✏️ by Shreyas JV on scifi.SE
 
10:13 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): ReactJS convention: ✏️ by Mark Goldstein on stackoverflow.com
 
@SmokeDetector tpu-
 
[ SmokeDetector | MS ] Potentially problematic ns configuration in body (1): Downloading image is always corrupted by Eagle Bound on stackoverflow.com
fp- feedback received on Cannot find insider transaction on chart [MS]
fp- feedback received
 
10:34 PM
!!/watch- blog\.vu-review\.com
!!/watch- trangtriquangcao\.com
!!/watch- (?-i:enuR9)(?#shorturl.at)
!!/watch- luckypatcher\.shop
 
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body; append -force if you really want to do that.
 
!!/watch- besthackersworld58(?:@gmail\.com)?
!!/watch-number- +1(323)-723-2568
!!/watch-number- (323)-723-2568
 
[ SmokeDetector ] Blacklists reloaded at rev 2e288a5 (SmokeDetector: Auto watch of +1(323)-723-2568 by Makyen) (running on teward/Osiris)
[ SmokeDetector ] Blacklists reloaded at rev 2b630e3 (SmokeDetector: Auto watch of (323)-723-2568 by Makyen) (running on teward/Osiris)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): is this how to read files in C because console app not closing correctly by brutus on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Teste de Integração .Net Core 2.2 by Giovanni Dalfre on pt.stackoverflow.com
fp- feedback received
 
11:12 PM
fp- feedback received
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Spring boot not processing Path Variable correctly by user1234567 on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword with email in body, potentially bad keyword in body, potentially bad keyword in title (59): We are a company in the field of games and applications on the iOS by MAZEN ABDUALAZIZ on stackoverflow.com
tpu- feedback received
teward/Osiris: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 2b630e3 (SmokeDetector: Auto watch of (323)-723-2568 by Makyen) (running on teward/Osiris, Python 3.6.9)
Restart: API quota is 9709.
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Why were dinosaur skeletons so light compared to mammal skeletons? by Brendan Golledge on biology.SE
fp- feedback received
 
11:35 PM
!!/watch- mazenabdual01(?:@gmail\.com)?
 
iBug/Sandy: Executing automatic scheduled reboot.
fp- feedback received
 
00:00 - 16:0016:00 - 00:00

« first day (2393 days earlier)      last day (1427 days later) »