« first day (3251 days earlier)      last day (866 days later) » 

22:00
-_-
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): Can you get paid for a new job after being constipted?‭ by Richard Phillips‭ on law.SE (@RyanM)
@SmokeDetector tpu-
!!/watch (?-i:^Richard Phillips$)
teward/Osiris: In getting MS post information, recovered from requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Read timed out. (read timeout=10.0)
[ SmokeDetector | MS ] Bad keyword in answer, potentially bad keyword in answer (89): Text file browser‭ by Noah Crusell‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): "Undefined columns selected" error message but head(data) shows names? ✏️‭ by Phyto‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body, repeating characters in body (63): Problema con el LocalStorage y los botones‭ by sTORGARO323‭ on es.stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in answer, link at end of answer, potentially bad ns for domain in answer (151): Can I bring prescription Adderall into Vietnam while on vacation there?‭ by Ashu Maxwell‭ on travel.SE
!!/watch premuimpharmacy\.com
[ SmokeDetector | MS ] Mostly punctuation marks in body (28): removing tweenmax js‭ by Hamoon‭ on wordpress.SE
fp- feedback received on [MS] removing tweenmax js
22:44
!!/blacklist-keyword constipt(?:ion|ing|ed|ee)?s?
!!/unwatch constipt\w*
!!/unwatch constipt\w*(?<!constipt(?:ion|ing|ed|ee)?s?)
@RyanM That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
22:56
!!/watch-force constipt\w*(?<!\bconstipt(?:ion|ing|ed|ee)?s?)
Needs the word boundary to not miss stuff like constiptconstipt, in case they are particularly skilled with regex...
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): React Landing Page render time is too slow. Wha can I do?‭ by Javi047‭ on stackoverflow.com
@RyanM A better formulation for this would be constipt(?!(?:ion|ing|ed|ee)?s?\b)\w*+, as that would result in the lookaround being tested only once, rather than at each character. Alternately, you could make the \w* possessive with \w*+, thus constipt\w*+(?<!constipt(?:ion|ing|ed|ee)?s?), which would effectively do something similar. However, using the look-ahead instead of the variable length look-behind is better, because MS doesn't support variable length look-behinds. Thus, the version which uses the look-ahead can more easily be searched for on MS.
23:34
!!/unwatch constipt\w*(?<!\bconstipt(?:ion|ing|ed|ee)?s?)
!!/watch-force constipt(?!(?:ion|ing|ed|ee)?s?\b)\w*+
@RyanM That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Manually reported answer (94): "threads" in Dart using Flutter for web‭ by Romulo Campos‭ on stackoverflow.com
@Makyen thanks, that's definitely better. I hadn't thought about the fact that it could be formulated as a lookahead, and the point about matching at one point rather than multiple is a good point too.
[ SmokeDetector | MS ] Bad pattern in url answer (56): How to run GUI apps with Windows Subsystem for Linux ✏️‭ by MOMO‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): how to get only one value from subquery‭ by Nana Suryana‭ on stackoverflow.com
23:57
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, potentially bad keyword in body, repeating characters in body (256): Express $1 + i + i^2 + i^3 + i^4 + ... + i^n$ in the form of $x + iy$ ✏️‭ by alefa‭ on math.SE

« first day (3251 days earlier)      last day (866 days later) »