@cigien 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.
@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.
@Makyen You clearly have scripts that generate watches (unless you're just that fast :)). I'm using the FIRE-additional-functionality script that double-beep, etc, have worked on, and that does do some automation, but not things like making the trailing gmail.com optional, or generating number watches. If you'd be willing, and able, to share, I'd quite like to try them out.
@RajaAnbazhagan I'm not sure if anyone responded to this, but it seems you've already created an MS account. In case you haven't read it, take a look at the introduction to participating. That covers a lot of what we do here, as well as the various ways you can participate. Feel free to ask any questions, and we'd be happy to answer.
@cigien I do have a bit. It converts each line in the chat input textarea into a !!/watch command. It recognizes a limited set of moderately common text formats and does more processing on them, such as making the trailing gmail.com optional. I've owed sharing it to Xnero for a long time (about a year and a half, IIRC).
It's been my intent to separate it out from the script in which I make all the changes which I've individually chosen to make to chat and put that portion that does the "watch-adjust" conversion in its own script (and also creating a few other scripts from functionality groups contained in that general script, and the general script I use for SE/SO main/meta).
I've been trying to allocate more time to actually accomplishing programming things (i.e. finishing, testing, and releasing), but I have a substantial number to run through, many of which are owed to people.
Today was mostly trying to get FIRE to the point where an intermediate release is a good idea, so I can do FIRE, AIM and a general dependency update for the Charcoal userscript repository (needed for a variety of reasons, including support of CI testing for a newly created PR in that repo, and so the dependency update task doesn't get substantially harder, or have to be completely redone). Unfortunately, I've spent substantially less time on that today than I'd hoped.
@Makyen Hmm, now that you mention it, I vaguely recall some parts of that conversation. It was before I used scripts at all, so I didn't pay much attention to it. Great to hear that we'll get to use some of that. I'm looking forward to it, but no pressure, whenever you get around to it works. Thanks in advance :)
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, blacklisted website in answer, potentially bad keyword in answer (267): Contact SelectOptions is blank by Rick on salesforce.SE
@RyanM Matched by (?:(?:m(?:[^a-z]|&\w+;)*)+(?:o(?:[^a-z]|&\w+;)*)+(?:t(?:[^a-z]|&\w+;)*)+(?:h(?:[^a-z]|&\w+;)*)+(?:e(?:[^a-z]|&\w+;)*)*(?:r(?:[^a-z]|&\w+;)*)+)?(?:f(?:[^a-z]|&\w+;)*)+(?:u(?:[^a-z]|&\w+;)*)+(?:(?:[^a-z]|&\w+;)*[ck])+(?<!fuck)(?<!fuk)(?:[^a-z]|&\w+;)*(?:(?:i(?:[^a-z]|&\w+;)*)+(?:n(?:[^a-z]|&\w+;)*)+(?:g(?:[^a-z]|&\w+;)*)+|(?:e(?:[^a-z]|&\w+;)*)+(?:[rd](?:[^a-z]|&\w+;)*)+)?(?:s(?:[^a-z]|&\w+;)*)* on line 3170 of watched_keywords.txt
[ SmokeDetector | MS ] Few unique characters in body, mostly punctuation marks in body, mostly punctuation marks in title, potentially bad keyword in body, repeating characters in body, +1 more (282): ;;;;;;;;;;;;;;;;;;;;;;;;;;; ✏️ by Greg OSullivanne on stackoverflow.com
@cigien That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Link at end of body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (101): What is Halden Belts? by Halden on superuser.com (@Ollie)
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
!!/report android.stackexchange.com/a/143271 "Undisclosed affiliation: user is the author of the linked post. While the last names don't match, the profile picture matches other SE/SO accounts by this user which do match the last name for the author on the blog. In the other accounts, the user has also been linking to their own content without disclosing affiliation."
