@lyxal Yeah, all the content is copied. It's generally preferable to leave a comment on the MS post (which you can do by replying to the report in chat), when the reason may not be obvious. I've flagged the answer as well. Thanks.
I'm also pretty suspicious about that being undisclosed affiliation given the similar pattern to their last spam answer and the similar general structure of the sites, but I can't find any proof.
@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 if you really want to add this pattern.
Hi, I have a question about the SmokeDetector and the underlying websockets, maybe someone can help or explain. Afaik the SmokeDetector uses the stackexchange websockets to get notified of posts, right? Do you have any idea wether or not it actually gets notified of every post / question or just some? It looks to me like stackexchange.com/questions?tab=realtime does not contain every SO question and neither does every question arrive in the websocket. Any ideas?
@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 if you really want to add this pattern.
@SmokeDetector I messed up - at first glace it looks like spam, but it's a homework question with awful, awful formatting. @tripleee - might be worth removing your spam flag on the post if you've cast one.
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer, blacklisted user (75): Is Windex safe for the windshield? by shivamaggarwal on mechanics.SE
[ SmokeDetector | MS ] Bad keyword in link text in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (85): Windshield replacement damaged molding? by shiva on mechanics.SE
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, +1 more (265): Defrag or Backup+Restore by Bhagyashri7M on dba.SE
@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 if you really want to add this pattern.
@tripleee User blacklisted (430340 on english.stackexchange.com).
[ SmokeDetector | MS ] Bad keyword in body, bad keyword with email in body, potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, +2 more (225): New Update 2021 Cisco | Dumpspass4sure.com by tom hanks on webapps.SE
@luk2302 While I personally haven't investigated the WebSocket wrt. this, the comments in SmokeDetector's code indicate it was noticed that not all SO, and only SO, active questions are included in the "all-SE" WebSocket subscription. In order to compensate for that, SD's code handles getting active questions differently for SO, so that all active SO questions are scanned, even if they are not reported through the all-SE WebSocket subscription.
If the WebSocket is not reporting some activity for other sites, then we would need to change the code.
Note: as mentioned above by @tripleee, we're aware that the "all-SE" WebSocket subscription doesn't include activity from any of the child meta sites. SD doesn't currently compensate for that.
@tripleee No need to be sorry about posting an answer/responding to someone's question. You were the person who was around and you gave the best information you had. There's really nothing wrong with that.
@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 if you really want to add this pattern.
[ SmokeDetector | MS ] Bad keyword in link text in body, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body (170): which is the best controller by Joshua Asaboro on gaming.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad keyword in body, potentially problematic ns configuration in body (3): C# connect to ssh by CrSerials on stackoverflow.com
