@Makyen That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@Olivia That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
> Numbers-only title, potentially bad keyword in body, potentially bad keyword in title ---------- Numbers-only title - Position 0-12: 380683017209 Potentially bad keyword in body - 380683017209 found normalized Potentially bad keyword in title - 380683017209 found normalized
### BrokenPipeError on teward/Solar Flare at 2019-04-19T12:54:10Z: [Errno 32] Broken pipe File "ws.py", line 196, in <module> a = ws.recv() File "/home/smokey/.local/lib/python3.6/site-packages/websocket/_core.py", line 310, in recv opcode, data = self.recv_data() File "/home/smokey/.local/lib/python3.6/site-packages/websocket/_core.py", line 327, in recv_data opcode, frame = self.recv_data_frame(control_frame) File "/home/smokey/.local/lib/python3.6/site-packages/websocket/_core.py", line 354, in recv_data_frame
### WebSocketConnectionClosedException on teward/Solar Flare at 2019-04-19T13:12:37Z: Connection is already closed. File "ws.py", line 196, in <module> a = ws.recv() File "/home/smokey/.local/lib/python3.6/site-packages/websocket/_core.py", line 310, in recv opcode, data = self.recv_data() File "/home/smokey/.local/lib/python3.6/site-packages/websocket/_core.py", line 327, in recv_data opcode, frame = self.recv_data_frame(control_frame) File "/home/smokey/.local/lib/python3.6/site-packages/websocket/_core.py", line 340, in recv_data_frame
[ SmokeDetector | MS ] Url-only title, bad keyword in body, pattern-matching website in body, pattern-matching website in title, potentially bad ns for domain in body, +3 more (396): atozfitnesstalks.com/keto-buzz-uk/ by wgsdloi on askubuntu.com
Recently in GDSE the spam increased a lot; there is company or person who is spamming about keto diet all the time; I flagged and downvoted a lot but isn't there any other way to stop this?
@ProcessedMeat the answer has links to MS, without saying that this is work of Charcoalm what is SmokeDetector, but that just there is a room where... spam arrives!
I've just passed a test in the Triage.
It was easy. The question had all the characteristics of a bad question, and probably the test in the body of the question was added just to fill it.
I was sure it was a test, and I've marked the question as "Unclear" (there were already four votes for "Un...
@Undo Are there any cron jobs on MS that run just on Friday➞Saturday? I ask because the two recent times that MS was IP blocked from the SE API were 7 days apart and we're coming up on 7 days from the last block. Both times spanned somewhere in 21:36:39 UTC and 02:36:42UTC on Friday➞Saturday. There have been no commits to MS since prior to the last block, so if the last block was for a legitimate reason, we haven't made any changes to correct what would have caused the last block.
OK. It certainly could be coincidence that both blocks happened on Friday➞Saturday. It could also be something on SE's side that makes them busier at that day/time and more likely to issue a backoff. Hmmm... that's around the time when SE runs several of their weekly tasks (e.g. the weekly Roomba). SE being busier at that time sounds more probable.
@Undo Based on my experience, getting a backoff is definitely inconsistent from the POV of the requests being made from a single IP. From the times when it's been more likely to occur, it certainly has felt like it is sensitive to current load levels on SE's servers. With similar SE API request patterns, I've seen a backoff with the first request or no backoff even after hitting an endpoint hard (e.g. 10 requests/s) for a few hundred requests.
Recently in GDSE the spam increased a lot; there is company or person who is spamming about keto diet all the time; I flagged and downvoted a lot but isn't there any other way to stop this?
I've just passed a test in the Triage.
It was easy. The question had all the characteristics of a bad question, and probably the test in the body of the question was added just to fill it.
I was sure it was a test, and I've marked the question as "Unclear" (there were already four votes for "Un...
