@SmokeDetector in case additional evidence was needed beyond just the face of the post, the site is "Private Equity Discussion by Eugene Gershman" and the display name eg_RE is presumably something to the effect of "Eugene Gershman Real Estate"
@Makyen A normalized version, {{'2348073245515'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +2348073245515 to determine which entries on the number lists match that pattern, which would tell you: Matched by 2348073245515 on line 2751 of watched_numbers.txt: 2348073245515 found normalized
@Makyen That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad keyword in answer, mostly punctuation marks in answer, potentially bad asn for hostname in answer, potentially bad keyword in answer, username similar to website in answer (196): Find equal elements in a list by myeducation wire on mathematica.SE
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (46): Mosasaurus Jurassic World Evolution 2 by zabela on mathoverflow.net
@cigien That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more (483): Regen CBD Gummies Reviews by BanjaminHenry on meta.SE (@Ollie @Ethan)
@JeffSchaller Please provide an adequate reason for rejection (at least 20 characters long) so the user can learn from their mistakes. Use -force to force the reject
@CanO'Spam The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@Nick The pattern contains an invisible U+202D whitespace character. In order for a "number" to make an exact match, the pattern must end with a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
@Machavity It looks like PR#8174 did not get approved, despite your command. I'm hesitant to approve it myself, as there a decent number of hits on-site: text search, URL search, code search
cc @CanO'Spam (see my previous message); are you sure we want to catch all those posts, or is there something more specific we could watch?
@JeffSchaller A good point, I should have checked that first. It would certainly seem more fitting to try and watch the 'CryptoTradeBot.7z' part but I am uncertain on the regex in all honestly
@CanO'Spam I'd suggest searching MS and searching SE overall to see what's out there. There's also the fine-tuned SE URL search (prepend URL:) and SE code search (prepend code:)
one tricky thing to remember is that the MS search will probably want to be a regex search, and the SE searches are not regex, so a typical MS search would be example\.com while the SE search would be example.com.
well, it's not always regex, but it usually is :) regex101.com is handy
The only other other thing :) about the MS search that I've learned is that you'll want to paste the regex into 3 fields: title, body, and username (checking the "regex" box as needed), and then select the "Use OR for text search" checkbox. That more closely simulates the actual smokey searches
