@iBug Having a system level block on this depends on what type of block. Is it one where the user gets a chance to rewrite/edit (e.g. the submit button doesn't work)? If so, then blocking it would be good. Is it one where the post just disappears? If so, then it would be bad. Do we have any statement as to what type of block we're should be considering when giving feedback? If not, it'd be nice for us to decide.
@Makyen At least, we could imagine a popup telling the user that the title is of low quality and cannot be submitted.
Other users' editing of the title would also be inappropriate as it's a full creation from scratch instead of an improvement of the current title, therefore IMO it should be blocked.
One of low quality (containing many spelling or grammar mistakes) would be salvageable via editing, but a zero-value and zero-content one (this one) would not.
@ArtOfCode I think we'rw good to delete the (now archived) theme repo, because I've merged the histories. Git blame would work. Live example: site vs theme. (cc @JF)
Note: GitHub website may show wrong histories for some files that are first deleted and then merged back, but if you checkout that commit and run git blame it will show correct information.
> Repeating words in body, repeating words in title ---------- Title - Repeated word: *asdfg* Body - Repeated word: *asdfg*
> Few unique characters in body, repeating words in body, repeating words in title ---------- Title - Repeated word: *hah* Body - Contains 8 unique characters Body - Repeated word: *hah*
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad ns for domain in body (295): Praltrix South Africa by ndkfsgad on apple.SE
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, +2 more (492): Regal Keto Uses by Josephine Quinn on drupal.SE
@TetsuyaYamamoto That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link following arrow in body, +3 more (589): KetoFit Canada Out there, by briamaxx on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (493): Tevida Canada the accurate news is by loryffannep on ham.SE
@tripleee That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, link at end of body, pattern-matching website in body, +2 more (491): Pure ravishing skin by user353661 on meta.SE
@tripleee That pattern looks like it's already caught by Bad keyword in body, Pattern-matching website in answer, Bad keyword in answer, and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (493): Teal Farms Garcinia Best for Weight loss by Yadayadaz on graphicdesign.SE
Also... I feel "Something went wrong when attempting to submit spam flag" message may be ambiguous or misleading. Can we provide proper reason like "You don't have account at target site" or "The post is already deleted during flag submission"?
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto At least the "deleted" case one should have already been present, but it appears I forgot to update the released version to the current response from MS. There are also some other cases which I should put in the released version.
@doppelgreener That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
@doppelgreener That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, +3 more (592): federalhealth.net/bio-x-keto-diet by user48897 on rpg.SE
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-21: essential cbd extract Body - Position 0-21: essential cbd extract Username - Position 0-21: essential cbd extract
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more (490): vimeo.com/292649026 by ThomasRyann on gaming.SE
@doppelgreener The !!/blacklist command has been deprecated. Please use !!/blacklist-website, !!/blacklist-username,!!/blacklist-keyword, or perhaps !!/watch-keyword. Remember to escape dots in URLs using \.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body (296): The 2-Minute Rule for slim body by Ieshamartin on astronomy.SE
