[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, pattern-matching website in body, phone number detected in body, +1 more (455): WHAT IS CANDY CRUSH HELPLINE NUMBER by asaddf adadd on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, pattern-matching website in body, phone number detected in body, +1 more (455): WHAT IS CANDY CRUSH HELPLINE NUMBER by asaddf adadd on superuser.com
@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.
@Makyen I hit an error while trying to run that command; run !!/errorlogs for details.
### NameError on teward/Solar Flare at 2018-12-14T17:25:47Z: name 'sys' is not defined File "/home/smokey/SmokeDetector/chatcommunicate.py", line 447, in __call__ result = self.__func__(*processed_args, alias_used=alias_used)
File "/home/smokey/SmokeDetector/chatcommands.py", line 354, in watch msg, force=alias_used.split("-")[-1] == "force")
File "/home/smokey/SmokeDetector/chatcommands.py", line 297, in do_blacklist metasmoke_down=metasmoke_down
File "/home/smokey/SmokeDetector/gitmanager.py", line 199, in add_to_blacklist
@Makyen I hit an error while trying to run that command; run !!/errorlogs for details.
@Makyen I hit an error while trying to run that command; run !!/errorlogs for details.
@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.
@Makyen Added customerssupporthelpline\.com to watchlist
### NameError on iBug/EC2 at 2018-12-14T17:25:14Z: name 'sys' is not defined File "/home/ubuntu/SmokeDetector_prod/chatcommunicate.py", line 447, in __call__ result = self.__func__(*processed_args, alias_used=alias_used)
File "/home/ubuntu/SmokeDetector_prod/chatcommands.py", line 354, in watch msg, force=alias_used.split("-")[-1] == "force")
File "/home/ubuntu/SmokeDetector_prod/chatcommands.py", line 297, in do_blacklist metasmoke_down=metasmoke_down
File "/home/ubuntu/SmokeDetector_prod/gitmanager.py", line 199, in add_to_blacklist
@SmokeDetector This answer is an exact duplicate of the user's other answer on this question (also reported by SD). I consider this TP, as it's desirable to have a system level block on exact duplicate answers on the same question.
@SmokeDetector This is a copy of this page. That page is under CC BY-SA 3.0 and the user included the copyright notice, so I can't consider it actual plagiarism. I've submitted an edit to put the contents in quote format and provide actual attribution. I've also raised a custom mod-flag on the duplicate answer leaving it up to the mods as to the acceptability of an answer that's entirely a copy of a webpage.
@thesecretmaster Further away from needing MS to use R/A flags, IMO. Previously, it was that all red flags on a post had to be R/A in order for the post to be excluded from audits. Now, because a single R/A flag will exclude the post from being an audit, having FIRE, and any other tools people are using, cast R/A flags when appropriately clicked will get us 95%+ (probably quite close to 100%) of the way to excluding R/A posts from audits.
That's unless and until we get to the point of casting 6 autoflags, at which point excluding R/A posts from audits once again becomes a significant issue. Whenever the suggestion of having MS choose between using spam and R/A flags for autoflagging has come up, the decision has repeatedly been that MS was going to just use spam flags, due primarily to the difficulty in programmatically determining which to use in each instance.
When it once again becomes an issue, my opinion is that it may be reasonably easy to make that determination based on existing detections with at least > 50% accuracy. So, as long as we are just trying to just be better rather than perfect, it shouldn't be all that difficult, when, and if, the time comes.
@K.Dᴀᴠɪs - Regarding the assistance you requested: My custom Mod flag about 5 posts 1 duplicate URL was accepted as helpful. User leiyang retained their account. YW.
!!/unwatch- (?:buy\b.{0,400}?</?a(?: [^>]*|)>\W*|\W*</a>.{0,400}?\bbuy)(?#buy before, in, or after a link within 400 characters; was 2145/2077/67/8 when watched)
!!/watch (?:(?<!<\/?code>.*)buy\b(?!.*<\/?code>).{0,400}?<\/?a(?: [^>]*|)>\W*|\W*(?<!<\/?code>.*)<\/a>(?!.*<\/?code>).{0,400}?\bbuy)(?#buy before, in, or after a link within 400 characters without code; when watched, was 3077/2878/194/14 minus 12/2/10/0: 2018-12-14T21:43Z, or so)
@ArtOfCode Regarding WB Knitting discussion here and Show your knitting Q&A, animation paid off: 3 badges, pinned at 200 (just as this day comes to an end) and a 'Award Bounty' has been set up by Nog for next-level knitting. Goes without saying: "I can't knit ..... ....".
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 22:01:02 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/1100963
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 22:01:17 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/42628
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 22:01:31 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/472001
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 22:01:45 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/132915
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 22:01:59 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/124711
