@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 word(s) if you really want to add the pattern you provided.
@SmokeDetector I guess they barely side by and FP is OK for that post, their previous post was deleted for no disclosure. User has all their posts deleted: stackoverflow.com/users/19838720/bhushan-kadam
@tripleee Doesn't going to the spammer page on MS show that already? i.e. it shows all posts related to that profile, even if the user had different usernames when each of the posts was reported. At least this works for a single site profile, I'm not sure if it works to link all profiles on the network.
[ SmokeDetector | MS ] Link at beginning of body, potentially bad ns for domain in body, potentially problematic ns configuration in body (43): Pro Full version by Pro Full versio on meta.SE (@Ollie)
@gnat While detecting such plagiarism is a worthwhile endeavor, and having something which scans all posts for potential plagiarism would be helpful, the actual SD instances really aren't the place for to do so. We do give TP feedback to plagiarism, when it is detected, but the project's goal doesn't include detecting plagiarism. At a minimum, our automated response to detected post, raising automatic red flags, really isn't the right thing to be doing on plagiarism.
It's possible to use the code for SD to have your own bot instance which can be modified to run other detections. We have plans to make that easier to do, but it's not something which has been worked on, yet. There are two things which are planed/desired which will help that:
A) being able to specify in the config file which sites you want to include in the scan/exclude from the scan and B) separating the current detections into a separate file (e.g. "detections.py") and then allowing those to be overridden by, say, a "detections_custom.py" file.
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username (192): Digital Marketing Agency by RGC SEO on stackoverflow.com
Blacklisting this user for suggesting an edit that includes their project and failing to disclose affiliation. I'm not convinced of bad intent, but I don't like that they tried to edit a link to their own repo without disclosure of affiliation. See: askubuntu.com/review/suggested-edits/1268484
Actually, I don't think they had bad intent, so I've custom flagged for a mod to give them a friendly reminder (I can't ping those that suggest edits AFAIK...)
