@Makyen That pattern looks like it's already caught by Pattern-matching email in answer and Pattern-matching email in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Pattern-matching email in answer, Bad keyword with email in answer, Pattern-matching email in body, and Bad keyword with email in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
Currently, there is a bug in the search feature on stackexchange.com. Namely, it always says that "Your search returned no matches." regardless of which term I type into the "Search all sites" box.
So now, we need to get the bug fixed so that "Search all sites" works properly again.
I do appreciate your mentioning it. I wasn't aware that it would be posted in other rooms. I wonder what the criteria was for rooms to report that into.
Interesting. It goes to debug rooms and the Tavern. Currently, that's CHQ, Charcoal Test, and the Tavern.
@Stormblessed Watching the domain and the similar text that's used as a product name/etc. is good, but the two regexes need to not overlap detections. For the one which is not intendted to detect the domain, you should add a negative lookahead to prevent detecting the text when it's the domain. So, for this, it should be !!/watch pushfry(?!\.com)
@Stormblessed Because, assuming that they each eventually qualify for the blacklist, they will be on separate lists for different detection reasons (i.e. bad keyword and blacklisted website). Unless we're specifically intending to, we don't want to detect the same text as the criteria for two different reasons.
@double-beep Because the user hasn't been repeatedly using multiple separate accounts. The username isn't all that unique. Blacklisting, even just watching, a username affects any other user that happens to be using that name. We should be quite conservative about doing blacklisting them in order to not bring undue scrutiny down on other users just because they happened to pick a potentially real name for their username. The more unique something is, the less we need to be concerned about that.
At a minimum, we should have such things on the watchlist for a good long while prior to blacklisting, unless the urgency of detecting ongoing spam justifies the added risk/potential negative consequences to other users. In this case, with relatively few detected posts, and no pattern of the user being aggressive about posting, the need isn't that great.
@Stormblessed It appears you're trying to watch a username. Again, unless you're specifically trying to detect a username that isn't the same each time, please use a regex that tests the entire username from start (^) to finish ($) and is case sensitive ( (?-i:name here) ). Note, however, that with only a single post, we wouldn't normally watch the username. If there's more than the single post, please tell me, but that's all I, and @double-beep, saw in MS.
[ SmokeDetector | MS ] Url in title, bad ns for domain in body, bad ns for domain in title, bad keyword in body, bad keyword in title, +6 more (787): wealthpediaa.com/flow-fusion/ by jguthv on puzzling.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +4 more (690): What is Keto Power Slim/ by aengelaucera on askubuntu.com
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more (688): supplecient.com/diamod-keto/ by zgakcrkh on security.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +4 more (590): Slim Physics Keto Diet by sandrachappell on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, +1 more (490): health More of the extra enhancements by binmasfija on askubuntu.com
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, body starts with title and ends in url, link at end of body, +2 more (590): ketoplanusa.com/insta-keto/ by JuliaGomez on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +2 more (493): thesanofi.com/flow-fusion-male/ by behigyao on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, bad pattern in url body, blacklisted website in body, link at end of body, pattern-matching product name in body, +4 more (685): Why it works like this? by patricianourse22 on superuser.com
[ SmokeDetector | MS ] Link at end of answer, pattern-matching website in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer, blacklisted user (212): What is the language of the Paradise? by hani on islam.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, +5 more (783): What is Keto Power Slim by jennifethompson on superuser.com
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, +3 more (689): ketoplanusa.com/insta-keto/ by MackColbu on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (196): Black Line Edge by user62080 on softwarerecs.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in title, potentially bad ns for domain in title (295): thesanofi.com/insta-keto/ by sklacruk on wordpress.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, +2 more (590): ketoplanusa.com/insta-keto/ by ThomasBean on askubuntu.com
@NisseEngström 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.
Currently, there is a bug in the search feature on stackexchange.com. Namely, it always says that "Your search returned no matches." regardless of which term I type into the "Search all sites" box.
So now, we need to get the bug fixed so that "Search all sites" works properly again.
