that's the one; the penultimate one was a manual report which was then also reported by Smokey and the one before that was the spam seed where I added the link to the site for context
@cocomac The pattern starts with whitespace. In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
@Vickel I might be wrong, but I don't think that will match the email in the above post due to the obfuscation (additional spaces in the email address).
@Vickel I mean I don't think that regex will match the string Jeffsilbert 39 @ gmail. Combecause that regex doesn't expect there to be whitespace there
Not sure. TBH, matching any character would likely be fine, as Jeffsilbert 39 is pretty unique. That said, we could also do something like Jeffsilbert[\W_]*+39[\W_]*+(?:gmail[\W_]*+com)?
ahhh, thank you regex101: "*+ matches the previous token between zero and unlimited times, as many times as possible, without giving back (possessive)"
@JeffSchaller A * quantifier is greedy. The regex engine will quickly consume all matching characters and then try to move on and match the next thing in the regex. If the next thing doesn't match, then the regex engine will "backtrack", giving up the minimal amount of what was greedily matched (typically one character, but could be a group of characters) and then try to move forward from there. In non-matching cases, the regex engine will backtrack to test at each character. Making the quantifier possessive means that the regex engine doesn't backtrack to each character that matches and then try to move forward again. It will only backtrack past all the characters which match what is being quantified. Using possessive can cause some unexpected things to happen in some situations, but if you're quantifying something and then immediately following it in the regex with something that can't match what's being quantified, then using a possessive quantifier will always save some computation (in failing cases, which tend to be more common than matches). In such cases, you are, effectively, explaining to the regex engine that there's no use in trying to match the rest of the expression from within the characters which were quantified, because that can't happen, due to what's written in the regex.
As an example, the regex a*b is better as a*+b, because "b" can never match "a", so there's no use testing at every "a" in "aaaaaaaaaac", because it's impossible for the next character to be a "b" when you already know that it was an "a", because it matched a* (working backward from where the "c" was found, which wasn't a "b").
So, we typically use a possessive [\W_]*+, because we almost always follow that with a character that matches [A-za-z0-9], which can never match [\W_]*+. Thus, there's almost never any use in the regex engine backtracking to test at each [\W_] character when it's known that the character it's giving up matches [\W_] and, thus, can't match the next character in the regex.
> Bad phone number in body, bad phone number in title, numbers-only title, phone number detected in title ---------- Bad phone number in body - 18883506579 found normalized Bad phone number in title - 18883506579 found normalized Numbers-only title - Position 0-11: 18883506579 Phone number detected in title - Phone number: 18883506579
Their username ("Free Keys Full Version") makes me think spam and not just off-topic. Possibly they would edit in a link to their website with more keys later
I'm flagging this post as ş̸̧̡̩͙̝͍̯̟̺͖̱̇͌͗̄̄͌́̉̏͊̚̚͜p̸̢̨̗̯͙̟̳̰̫̞͍̳̯͓͋͋͜͝ą̶̝̘̞̙̮͎̯͈̱̿̾̎̍̇͝m̶̨̢̻̘̖̦̬̤̦̳̪̖͉̌͜ͅ because h̵̡̐̄͐̏͑̋͒͋̃̾͊e̸̛̹̜̗͉͚̞͒̒͊͋͛̂̕̕ ̸̡̡͓̰̺̱̠̼̥͔͖̥̰̬̠̽͋̆͋͑̔̚͝c̸̢̨̛̗̫͕̞̞͖̱̈́̿̄ơ̵̦͇̞̰͕͓̯̫͙͍̦̭̯͊͗̃̔͆́́͋ṃ̷̢̝̦̠̩͓̙̇̆̈́́͋̀͂̂͊̽̚͝ē̵͍̮͇͉͕͙̳͈̪̟͍̍̀́̐̋͌̕̕͜͠ͅs̸̯͍̪͂͋̇͆́̅̋́̇̅̽̕͠͠͝ͅ.
