we don't have any good process for that, I was looking at tooling for it a few years ago but I ended up bombarding metasmoke with queries to the point where it was not sustainable
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, link at end of answer, potentially bad ip for hostname in answer, potentially bad keyword in answer, +3 more (305): GPO to disable Windows XP tour popup by raushni gupta on serverfault.com
@tripleee 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 pattern in url body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad ns for domain in body (88): kem mắt klirvin có tốt không by lee ho on superuser.com (@Ollie)
@Ollie 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.
@tripleee Searching MS for "o\.bike(?<=https?://(?:\w+\.)*o\.bike)" with the regex button checked throws errors. Also, wouldn't just "o\.bike" suffice?
The quota_remaining property was not in the API response. Error: no method found with this name at 16:07:46 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
teward/Osiris: In getting MS post information, recovered from `requests.exceptions.ConnectionError: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Max retries exceeded with url: /api/v2.0/posts/urls?key=[METASMOKE KEY REDACTED]&filter=GHOOIJGNLKHIIOIKGILKIJGHFMNKKGFJ&urls=%2F%2Fsuperuser.com%2Fquestions%2F1684483%2Fregex-group-needs-to-stop-at-first-occurence%2F1745026%231745026 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7 fbd1daa7220>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))`
@Ollie the anchoring is to prevent accidental matches on anything ending in o\.bike, I'm not entirely sure off the top of my head what the bookending really looks like but IIRC I copied that from another short domain which had something similar
dunno about the MS error, the PCRE support in there isn't entirely robust but I can take a closer look tomorrow
@Ollie @tripleee Yes, searching for that exact regex on MS isn't possible, because MS doesn't support variable length lookbehinds. In order to have a search which will work on MS, you will need to convert the regex into something that is effectively similar, at least as far as overall matches.
The first thing to note is that the exact text of the match doesn't need to be identical, because on MS we only care if the post matches or not. So, while for the watch we want to have "o.bike" be the actual matched text, it's fine for the search on MS to actually match "https://foo.o.bike". Thus, we can convert o\.bike(?<=https?://(?:\w+\.)*o\.bike) to https?://(?:\w+\.)*o\.bike, which is what's required by the lookbehind and includes the entirety of the non-lookbehind text.
We then add the ending bookending of (?:\b|$), but not the beginning bookending, as the lookbehind isn't affected by the beginning bookending and all cases in the possible matched text effectively match the beginning bookending where it would exist for the main matched text. So we have a regex on MS of https?://(?:\w+\.)*o\.bike(?:\b|$),
I've never done an all spam report before. Is a user like jeff who has 11 answers all promoting the same tool (sometimes with the link obscured by code fences) the correct use case for that?
A few of those questions are also off topic so it's also a nice chance to clean up some tool requests as well.
I appreciate your help. I didn't want to mess up that command. I was fairly confident that was the appropriate use, but I'd generally prefer to get confirmation first than try to undo it afterwards.
[ SmokeDetector | MS ] Few unique characters in body, luncheon meat detected, no whitespace in body, potentially bad keyword in body, repeating characters in body (296): uid not getting updated ✏️ by harrie on stackoverflow.com
