« first day (2662 days earlier)      last day (1150 days later) » 

@Makyen >_> Did I bork my SE search, then? I could've swore I came up with no results on a search for it. Thanks for looking deeper and correcting that. I'll try and be a bit more careful in my SE searches... I swear that page hates me sometimes.
 
Can confirm that @Spevacus. Works just fine for me.
 
@Spevacus For SE searches, it's necessary to separately try all of in URLs, in text, and in code
 
6:20 PM
[ SmokeDetector | MS ] Bad phone number in body (100): Netgear technical support 1 by Max on superuser.com
 
tpu- feedback received on [MS] Netgear technical support 1
 
@Xnero (cc @Spevacus) The answer is, as usual, "it depends". A "possessive" quantifier means that what is being repeated will always match all of the times it can and never fewer than the maximum (or none, if none is permitted, e.g. *+). Making a quantifier possessive is a good thing to use when the next part of your regex after the quantifier can't match the thing you're quantifying (e.g. we use it for [\W_]*+ when followed by an alpha-numeric character, which [\W_] can't match).
For non-possessive, non-lazy quantifiers, the regex engine will first try grabbing all the text matching what is being quantified. If it then doesn't match the entire rest of the regular expression, the regex engine will backtrack to the quantified text and try again to match the entire regex with one less of the thing being quantified. If it continues to not match the entire rest of the regex, then the engine will continue backtracking with progressively fewer of the quantified text.
If the next text in the regex can never match what it being quantified, then all of that backtracking is completely useless and just wasted processing. Making the quantifier possessive will prevent that wasted processing from happening. That's the primary reason for most of the times we use possessive quantifiers.
However, possessive quantifiers also have other overall effects and uses. Using them can be important to a regular expression working the way you intend (e.g. this), or it can also cause the regex to do something unexpected, including both unintended matches and failures to match. As usual, it's a good idea to test regexes against a substantial sample of the text which you are wanting to use them on to see if they are really doing what you desire.
 
[ SmokeDetector | MS ] Few unique characters in body (94): Efficiently formatting discord.py ✏️ by Apollo on stackoverflow.com
 
tp- feedback received on [MS] Efficiently formatting discord.py
 
Your detailed explanations are always awesome to read, Makyen. :)
8
 
6:35 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer, toxic answer detected (81): Only Black & White text in Python editor in ArcGIS for Desktop? by BHH on gis.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, potentially bad ns for domain in body, +2 more (491): Ontario Farms Hemp Oil Reviews, Side Effects, Benefits and Price by ontariofarmsh on meta.SE (@Ollie)
[ SmokeDetector | MS ] Post is mostly images (15): How can I put my text and image in the middle of a div? by N3v4da Stone on stackoverflow.com
 
6:55 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to make graphic overlay elements responsiveness in live preview Camera? by Alan Itzep on stackoverflow.com
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Some of my villagers on Minecraft are not restoking by Soumil30 on gaming.SE
teward/Osiris: Executing automatic scheduled reboot.
 
@Spevacus Thanks. I'm glad they're helpful.
 
7:02 PM
Restart: API quota is 10749.
[ SmokeDetector | MS ] Bad keyword in link text in body, potentially bad keyword in body (70): Pull records in excel that don't match as a list by SO2605 on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in username (89): Is there no further development on H2? by Binfer on stackoverflow.com
 
7:20 PM
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer (2): Copying Production Recycle bin data to Sandbox without undelete in Prod by firdous flower on salesforce.SE
[ SmokeDetector | MS ] Bad keyword in link text in body (69): How can a "gold" coin look nothing like gold? by Wannabe Goldbug on money.SE
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Scrapear una plataforma de streaming con BeautifulSoup, posible? by tadeo soresi on es.stackoverflow.com
 
@SmokeDetector The system doesn't allow jsfiddle links without code. Hence they used the shortened link. Not spam but the question needs to be closed.
 
8:01 PM
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How can a Pure Titans recover the full body after extended period? by Secretwind98 on anime.SE (@AndrewT.)
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Growing wheat from grains by shuaybi on gardening.SE
 
@SmokeDetector It's vandalism
 
sd tp-
 
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Call to undefined function mysql_pconnect() by hosktech on stackoverflow.com
 
8:28 PM
[ SmokeDetector | MS ] Link at beginning of answer (34): Opening Realm file in browser always requires an encryption key by FWilliam on stackoverflow.com
 
9:01 PM
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad keyword in answer (35): Is Scrooge McDuck immortal? by Elijah Page on scifi.SE
[ SmokeDetector | MS ] No whitespace in answer, potentially bad keyword in answer (97): Figure out the code by Kailen Navarro on puzzling.SE
[ SmokeDetector | MS ] Bad keyword in link text in body, potentially bad keyword in body (70): google sheet vlookup a cell that do not contain multiple value by zongshita on stackoverflow.com
[ SmokeDetector | MS ] Link at beginning of body (42): SQL poblem: how to define difficulties by David Dongdong Chang on stackoverflow.com
 
9:31 PM
tpu- feedback received on [MS] Is Scrooge McDuck immortal?
 
[ SmokeDetector | MS ] Bad keyword with email in answer (84): Change order status string from "Completed" to "Shipped" by HANY FOUAD on drupal.SE
 
10:00 PM
Makyen/EC2-num02: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 1184a33c7 (Makyen: This is the MS instance, so needs to post feedback) (running on Makyen/EC2-num02, Python 3.6.12)
 
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Cómo puedo hacer un filtro de busqueda en React Native? by Xon on es.stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in answer, no whitespace in answer, repeating characters in answer (264): fetching always throw an error inside AuthStateChanged by fumbling cow on stackoverflow.com
 
[ SmokeDetector | MS ] Mostly punctuation marks in answer, repeating characters in answer (117): Should I inform my bosses that I'm about to start doing a PhD research? by user135780 on academia.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Does confessing make sense? by helpmepls on workplace.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to login to site and get a cookies by python by rayan Moustaf on stackoverflow.com
 
10:36 PM
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Mobile Validation by Deepak Raj on salesforce.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): How to add different versions of logo to wordpress website by Rajat Sachdeva on stackoverflow.com
 
@Ollie grrrrrr
;)
Still need something?
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): is it possible to get this texture in cycles? by darkbean on blender.SE
 
@Undo Other than the real desire to poke me (reasonable), the rest was joking around and I did not see anything else specific, or even general. (i.e. definitely nothing specifically actionable)
 
Danke :)
 
10:58 PM
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Did Krishna marry Rukmini at age of 8? ✏️ by akshay pawar on hinduism.SE (@Pandya)
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Is a lack of "rules" dangerous for cryptocurrency by Nai on economics.SE
 
np :)
 
tp feedback received on [MS] Figure out the code
 
11:18 PM
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector | MS ] Pattern-matching website in body (96): Twilio Twimlets Forward Twice and Voicemail - Voicemail Greeting called from Asset by Marea on stackoverflow.com
 
11:49 PM
iBug/Lily: Executing automatic scheduled reboot.
 

« first day (2662 days earlier)      last day (1150 days later) »