« first day (3371 days earlier)      last day (435 days later) » 

4:01 PM
sdc unwatch pip install AppOpener
 
sdc watch pip[\W_]*+install[\W_]*+appopener(?#Several TP on SO; confirmed by site mod)
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How do you change the font size on Canva?‭ by Victoria Lane‭ on askubuntu.com
@Pilot6 Post 1: Already recently reported [ MS ]
 
4:03 PM
!!/watch fontsonic\.com
 
@Pilot6 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.
 
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 6b79b1731 (Makyen: Ping Makyen for some new metasmoke users) (running on Makyen/MS-Relay, Python 3.11.0)
 
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): ErrorDocument not working for any error. Ubuntu Apache‭ by La Phyzz‭ on serverfault.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): The balance between Renting and Buying ✏️‭ by Jason Chan‭ on money.SE
 
4:19 PM
@SmokeDetector tpu- undislcosed affiliation (they're listed in myperch.io/about), and the phrasing in the answer is intentionally misleading. Custom flagged.
sdc watch myperch\.io
 
[ SmokeDetector ] Blacklists reloaded at rev 5fd7875ae6 (SmokeDetector: Auto watch of myperch\.io by cigien) (running on teward/Thoth)
[ SmokeDetector | MS ] Potentially bad keyword in body, blacklisted user (71): Microsoft Office Home And Business 2019 CD Key for MAC Global‭ by Buffcomsoftware‭ on superuser.com
 
4:35 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): GUI not updating when repaint()method is called‭ by rmd28‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Streamwise Pressure Gradient and Curved Walls‭ by Josue‭ on physics.SE
 
@cigien I intentionally did not do that, because this is a command that is typed in as code, and it makes no sense for it to be separated with anything other than space characters.
If it were to happen to appear in some other context with hyphens or other non-space separator characters, I would not want it to be caught, because that would not be the same spam.
 
Ok, I'll change it. The change was just to add the comment.
 
Oh, I see. I assumed the change was to add the [\W_]*+ in place of the spaces because that's normally what would be wanted.
 
sdc unwatch pip[\W_]*+install[\W_]*+appopener(?#Several TP on SO; confirmed by site mod)
 
4:43 PM
I also thought that the discussion around the watch command would be sufficient documentation, but I suppose I've no legitimate objection to including the comment inline.
 
sdc watch pip\s*+install\s*+appopener(?#Several TP on SO; confirmed by site mod)
 
That's not right, either. :-| No one is going to type "pipinstallappopener" in an answer...
 
The discussion is better than nothing, but having a comment when doing a bisect can save time rather than digging through the transcript.
@CodyGray True, but is this version going to detect anything that we don't want to?
 
4:46 PM
You don't have to dig through the transcript. You just do a search on exactly what "bisect" returns you to see where it was watched. Boom, right there, you have the information at your fingertips.
Is it going to detect anything that we don't want to? I don't know! It certainly could, that's the whole point.
The original detected exactly what it was intended to detect and nothing more. I find it frustrating that you keep trying to "overrule" or "improve" what I typed, especially a second time after I already pointed out that I knew what I was doing.
The whole reason it was revisited was because someone raised concerns about the original watch resulting in too many FPs because it wasn't targeted enough. Why would we make the mistake a second time of knowingly making the second watch less targeted than it could be?
 
@SmokeDetector f But why are you editing in product links to someone else's answer
 
Sorry, I'm not trying to step on your toes or anything. Would pip\s++install\s++appopener be ok with you? Someone could easily type an extra space in between and it would be valid, and something we want to catch.
 
"Someone" could, I guess, but not the individual who posted this same thing a dozen or so times, probably copy-pasting it. But I guess it's a valid point that if they return after a hiatus, they might use a different format or make a typo or something. It doesn't matter all that much either way, I'm just irritated at having to revisit it and discuss it multiple times.
 
I would ideally prefer it if one of those spam posts were reported to MS. It would be completely clear why we're watching it then.
 
4:51 PM
Yes, but then someone has to go through and undelete them, report them, then redelete them, which has its own consequences, beyond being tedious work for no benefit whatsoever.
 
Well the benefit is that the original discussion would likely not have happened at all. I understand it's extra work to do the undelete, etc, which is why I went with adding a comment to the pattern.
sdc unwatch pip\s*+install\s*+appopener(?#Several TP on SO; confirmed by site mod)
sdc watch pip\s++install\s++appopener(?#Several TP on SO; confirmed by site mod)
 
@CodyGray Hmm, what consequences are you referring to? I wasn't aware there were any.
 
Well, for one thing, a user cannot raise a flag of the same type multiple times, even if they're a moderator. So, what often happens is that I'll be the one who nuked something (before realizing it wasn't reported to SD), then if I undelete it and report it to SD, beyond the tedium of having to remember to unlock it first before I can re-flag it, I can't even re-flag for the original reason.
Fortunately, I can re-flag for the other red-flag reason, but the choice of red flag reason has consequences, such as eligibility for an audit.
That may or may not apply in this case, but determining whether it would is just more time I would have to spend looking at it and evaluating it before taking any action.
The action I originally decided to take, which amounted to posting a simple explanation in here that I deemed more than sufficient for anyone who was curious, and watching the minimal thing necessary to detect the existing instances of spam, was way less work than any other alternative, and, again, I thought it would be more than sufficient, because why would someone second-guess this?
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Single Shot Rifle‭ by Ronnie Mcnutt‭ on stackoverflow.com
 
5:02 PM
Speaking strictly for myself, I don't assume that a watch is correct if I can't find any tp for it on MS (mistakes happen often enough). If there's no tp and the actual watch that was made doesn't indicate anything about the reason, I have to then go through the transcript, and hope that the rationale is somewhere close to where the watch was made. I was just trying to reduce future work for someone looking at such a report.
 
@cigien If only someone had said something that would explain that cognitive dissonance. Oh wait!
I really don't buy the argument about "go through the transcript" when it's like the very next message before/after the watch, and when the watch is trivially findable with the search function.
 
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (159): Reservation category of people born out of inter-caste marriages‭ by user49004‭ on law.SE (@RyanM)
 
5:04 PM
That's just not using the tools in front of you. Unless, I suppose, chat search is down, which does unfortunately happen sometimes.
I deliberately include the rationale next to where the watch is made. That's a pretty common pattern that a lot of folks use, in my experience. Not looking for this and needing/expecting to find an inline comment in the expression itself is strange and unexpected from my point of view.
But, again, my principal complaint wasn't even adding the comment, but rather changing the watch itself by making it more inclusive when it was intentionally not made so inclusive. I guess that needed to be explained in the inline comment, too? Maybe I should just append a (?# sic)... would that help?
 
No, that doesn't need to be explained. I read the discussion and thought that adding the pip install was meant to make it less inclusive, not that the "exactly one space between the words" was part of that, which was my bad.
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How to make bitcoin hd wallet in typescript?‭ by aulneau‭ on bitcoin.SE
 
Re the inline comment: I do test and bisect a lot, and only search through the transcript rarely, when I want/need some additional context. I would personally find an inline comment when I bisect something to be a lot faster than searching the transcript.
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): How to prevent scrolling up when clicking an anchor link to show hidden div‭ by Ana Maciel‭ on stackoverflow.com
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected, blacklisted user (229): Legality of the right to refuse admission by a privately owned restobar‭ by Oppressed dalit stole your job‭ on law.SE (@RyanM)
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How can you download Android apps and games with ease?‭ by Apkxu‭ on stackoverflow.com
 
sdc watch-force apkxu\.com
 
@cigien 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:19 PM
[ SmokeDetector | MS ] Few unique characters in body (95): Hi I need help on a Statistics question ✏️‭ by Penny Smith‭ on mathoverflow.net
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): list-style outside isn't displayed but inside is‭ by Md. Sanbir Hossain‭ on stackoverflow.com
 
@cigien Considering that bisect is a slow and resource-intensive command, I think it would actually be preferred that you use the chat search in preference to that when it is trivially possible to do so. But perhaps this is not actually a big deal. It makes more sense to do that works for you. I also use bisect a lot. But I definitely do try to avail myself of existing content.
It is very common for both Makyen and tripleee to include messages along with their watches explaining the rationale, and that's where I learned (imitated) it. If you're not routinely looking for that, you're missing out on a lot of information that people took the time to attempt to provide.
 
To clarify, I'm only talking about adding inline comments on watches for which there are 0 tp on MS. I don't add inline comments generally. Yes, if I'm looking for more rationale about a watch, I would look through the transcript.
If I shouldn't be adding inline comments for such situations either, that's not a problem, I won't do that anymore. It just seemed to be helpful in these situations.
 
5:30 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): Consistency of the marginals ✏️‭ by Grumpy Cat‭ on stats.SE
 
fp- feedback received on [MS] Consistency of the marginals‭
 
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially problematic ns configuration in body (2): agency marketing clearwater smgcreativos‭ by Yojhan hernandez‭ on webmasters.SE
 
sdc watch smgcreativos\.com
 
5:50 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer (2): How to create AI Images (Midjourney) by code?‭ by e.bicharri‭ on stackoverflow.com
 
6:15 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): What format to use for YOLOv7 object detection annotations?‭ by FluidDynamicsQuestion‭ on ai.SE (@Mithical)
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): I can't create a simple looker studio pie plot ✏️‭ by Lucas Fonseca‭ on stackoverflow.com
 
6:30 PM
[ SmokeDetector | MS ] Link at beginning of body, potentially bad keyword in body (42): I want to remove woocommerce single Product descripton tab in product page in mobile view like desktop‭ by Beauty Banu‭ on stackoverflow.com
 
@cigien Inline comments in the watch/blacklist entries can/should be used wherever it's believed that having such a comment will be helpful for someone looking at the entry in the future. I've seen no indication that using them has any impact on SD. Using them on MS can have an impact, but the main place that I've seen that happen is in the more involved spam wave regexes. I wouldn't add them to everything, but just when it reasonably seems it might be useful to have in the future.
 
!!/watch unique[\W_]*+care[\W_]*+endo
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): WorkbookFactory.create(inputStream)‭ by Mauricio Davalos Llave‭ on stackoverflow.com
 
naa- feedback received on [MS] WorkbookFactory.create(inputStream)‭
 
7:13 PM
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)
 
7:27 PM
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): How can I get data from API in Swift?‭ by Oktay Evin‭ on stackoverflow.com
 
7:37 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): React reCaptcha - ERROR for site owner: Invalid site key‭ by Jeremiah Haastrup‭ on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted user (70): Scraping data [sport results] from HTTPS website‭ by nodeCrawler‭ on stackoverflow.com
 
8:04 PM
teward/Thoth: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 92519366ba (SmokeDetector: Auto watch of unique[\W_]*+care[\W_]*+endo by tripleee) (running on teward/Thoth, Python 3.10.6)
Restart: API quota is 69085.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Din Rail Mount On/Off Switch or toggle button‭ by thegreatyonini‭ on electronics.SE
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer (2): Djinni in modern times ✏️‭ by Robin‭ on scifi.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to find new customers in Microsoft Excel?‭ by sam‭ on stackoverflow.com
 
9:22 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Why surjective functions is retractive and also injective one?‭ by Peter HU‭ on math.SE
 
10:05 PM
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 6b79b1731 (Makyen: Ping Makyen for some new metasmoke users) (running on Makyen/MS-Relay, Python 3.11.0)
 
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad ns for domain in answer (37): How to describe this text alignment feature with varied font sizes‭ by Forrest O.‭ on english.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Swapping two nodes in a red-black tree ✏️‭ by Skeet‭ on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): GoogleSheets API does not work. It does not let to strikethrough with API‭ by C4H7Cl2O4P‭ on stackoverflow.com
[ SmokeDetector | MS ] Pattern-matching website in answer, 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, +1 more (81): How do I make a div full screen?‭ by mehdi derakhshan‭ on stackoverflow.com
 
10:22 PM
naa feedback received on [MS] How do I make a div full screen?‭
 
@SmokeDetector tpu- undisclosed affiliation for canseo.ir
!!/watch canseo\.ir
 
@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.
 
10:37 PM
API quota rolled over with 67698 requests remaining. Current quota: 79999.
stackoverflow: 2374
math: 1285
ru.stackoverflow: 511
physics: 448
superuser: 351
electronics: 346
askubuntu: 333
unix: 322
stats: 320
es.stackoverflow: 319
tex: 268
gis: 243
mathoverflow.net: 189
serverfault: 176
dba: 167
pt.stackoverflow: 156
blender: 150
diy: 148
law: 141
ethereum: 136
ell: 135
salesforce: 130
apple: 127
mathematica: 123
english: 113
worldbuilding: 110
meta: 101
philosophy: 99
wordpress: 93
cs: 88
scifi: 83
codereview: 81
datascience: 75
academia: 72
crypto: 67
magento: 66
christianity: 66
 
11:08 PM
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Are there open data for long-term potentiation/depression experiments?‭ by Joram Soch‭ on psychology.SE
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Save a Website Search Result List to txt file ✏️‭ by 934293924‭ on stackoverflow.com
 
11:33 PM
 
!!/bisect serum
 
@CodyGray 'serum' is not caught by a blacklist or watchlist item.
 
Not spam, as far as I can tell, but is this a good-faith answer?
 
@cocomac I don't think so. It gets weird at the end. On the second thought, the entire thing is weird, for multiple reasons.
Still, I wouldn't give TP feedback on that because it's not something that we would want (or reasonably expect) to block at a system level.
 

« first day (3371 days earlier)      last day (435 days later) »