OK. So that makes sense. The \b token at the beginning is keeping it from matching "veryepicdude", but "yepicdude" is matched. So far, so good. Why, then, does it report this? The "position 3-12" suggests that the \b token isn't actually serving any purpose.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body, potentially bad keyword in body (389): Carolina Farms CBD Oil by AliciWalk on apple.SE
@Makyen 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.
What makes it difficult is that the state of the watch- and blacklists can change after the report, so you have to go trying to piece together what has changed and how that affects things.
Would be super nice if there was some kind of git blame, but I realize that's way too optimistic.
@CodyGray Well, you can always clone a local copy of the repository and use whatever tools you want locally. GitHub's interface for git blame is insufficient to the task for the watchlist, due to the size of the file and number of changes, but I'll often use grep to search through the files, or other git tools to search through the commits.
@cigien 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 answer, blacklisted website in answer, pattern-matching website in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, +1 more (323): What is weight decay loss? by My fitness Web on stackoverflow.com
@CodyGray Strategies I've used with some success include: 1) searching Charcoal HQ for the string that was matched but now isn't (here, "veryepicdude"), 2) looking at the last few commits for either all of SD or the relevant file (here, blacklisted_usernames.txt).
here, the first one would've worked better, since I had the same "wat" reaction and bisected it to see why it got picked up
alternately, looking at the bottom of the relevant file, since commands here always append to the end
@cigien To be honest, I did not look. I assumed based on the general pattern that was some sort of general service, like YouTube or Medium or whatever, and that the second part was a user ID. I didn't actually visit the website.
@RyanM I did search for "veryepicdude". It found nothing. I also searched for "yepicdude". The only things they found were my own messages.
@CodyGray Ok. I didn't actually visit the website either, but there's no FP on SE, so if it urns out to be a general service, and starts generating FP, I'll reevaluate.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, link at end of body, pattern-matching product name in body, +1 more (480): Synapse XT review 2021 by Rahul Kumar Mahto on meta.SE (@Ollie)
[ SmokeDetector | MS ] Url-only title, bad ip for hostname in body, blacklisted website in body, body starts with title and ends in url, link at end of body, +4 more (593): geehiibrain.splashthat.com/ by ayana everet on askubuntu.com (@Ollie)
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in username, link at beginning of answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (211): Ajax load page without refresh by satta matka final on stackoverflow.com
