@Xnero I actually worked on this. I had allowed myself to mentally put it in the "completed" category, but it looks like I never got it into the codebase. I assume because the JavaScript CI test failed and I switched to fixing that, which did eventually get fixed. I even whent looking for the cod on GitHub after seeing this message, but then found that, no, I didn't actually submit it after fixing the JavaScript issue.
I'll take a look again at what I wrote and see if I can submit a PR for it, or at least verify why I didn't submit it. I'm sorry I ended up dropping this.
I'd much rather have something deterministic, rather than have it be that we're randomly choosing to assign to Core or non-Core.
@SmokeDetector While the answers sort of provide a service asked for in the question, 3 answers have been posted in quick succession, and the 3rd doesn't disclose. Calling this spam.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, potentially bad keyword in body, potentially problematic ns configuration in body (264): Top Construction Companies in Hyderabad by user9844516 on stackoverflow.com
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= (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f4cda46f730>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
@Ollie That pattern looks like it's already caught by Bad keyword in body, Bad keyword in answer, Potentially bad keyword in body, and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 8-20: company.site Potentially bad keyword in title - Position 8-20: company.site Potentially bad keyword in username - Position 8-20: company.site Url in title - Position 0-20: https://company.site
@Xnero There is a substantial amount of explanation in both the PR and in the code, particularly of what the code is intended to be doing (i.e. such that Ruby knowledge is not all that needed). I'm willing to provide more explanation, but I'd appreciate you being more specific as to which part you don't understand.
@SmokeDetector This is the user's second inclusion on SE of a link to this site which is at least not directly related to the question/answer. There's also at least one instance off-site of the user promoting the domain, based on a Google search. I'm going with TP.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
