[ SmokeDetector | MS ] Url-only title, blacklisted website in body, link inside deeply nested blockquotes, potentially bad ns for domain in body, potentially bad ns for domain in title, +2 more (299): confidentpedia.com/velofel-south-africa/ by JohnGlase on askubuntu.com
@ByteCommander Yeah, I saw that after I hit send. I also then did a search on SE for "odataware". As you had already determined, "odataware" by itself should be fine.
@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.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (393): interactive prompt internal error by Ulfatbos64 on askubuntu.com
@Makyen I reported a "fp" on m.erwaysoftware.com/posts/uid/unix/536252 and added a note to it. It flagged because Pattern-matching website in body - Position 1650-1660: dietpi.com, but dietpi.com by itself seems to be OK. Not sure how to correct the regex.
@JeffSchaller Potentially bad keyword in answer - Position 1217-1536: </a>. There's nothing worse than not being able to get a good recording because your soundcard isn't low latency or powerful enough to keep up.</p><p>The only time I ever put distortion effects on an acoustic guitar sound it didn't come out too well but in principle there shouldn't be a problem. You could either buy
@Makyen 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.
@Makyen 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.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Pattern-matching website in body, Potentially bad keyword in answer, and Pattern-matching website in answer; append -force if you really want to do that.
@Makyen 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.
@Makyen 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.
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 12-35: thiastravelservices.com Potentially bad keyword in title - Position 12-35: thiastravelservices.com Potentially bad keyword in username - Position 12-35: thiastravelservices.com Url in title - Position 0-35: https://www.thiastravelservices.com
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 7-18: uiux.studio Potentially bad keyword in title - Position 7-18: uiux.studio Potentially bad keyword in username - Position 7-18: uiux.studio Url in title - Position 0-16: http://uiux.stud
:51405891 Please do not have your first attempt at watching or blacklisting something use -force. The checks that are run when -force is not used provide a valuable double-check that what you are doing doesn't conflict with or duplicate already existing detections. Note that I rarely have my first pass at watching/blacklisting something be -force, even when I know that it will be caught by some reason.
For example, there are some I add where the regex will definitely be detected by another detection, particularly when I've designed the regex to explicitly exclude detecting the same thing as the other detection. I still, usually, don't use -force when adding those in order to see if the automatic pass at detections finds anything I'm not expecting.
@Stormblessed Other than it takes a Room Owner or Moderator to remove stars (after the stars are locked in, so the person who added it can't remove it), I have no information. I'd assume that one of those able to do so removed the star because they felt it shouldn't be highlighted. That could be for a variety of reasons. It could be just that it was no longer something that people needed to see/act on.
^ These are both expected. I was forcing CircleCI to rebuild the caches used for the master branch. At least one of the rails-tests' caches was broken and causing the tests to fail prior to actually executing.
