@Undo it would be nice if we were able to deploy MS even if it isn't working. Or at least be able to restart it. I can see how that would be very useful.
@WELZ I assume that where you used {+}, you were trying to indicate 1 or more digits. That would be done with \d+ or \d{1,}. The {}, a "quantifier", is used to indicate a specific number of times. The general format is {n,m}, which is some number of times between n and m. {5} is exactly 5 times. {5,} is 5 or more times. {5,8} is 5 to 8 times.
{,8} may, or may not be a valid quantifier, depending on the Regular Expression engine you're using. It's valid in Python and means 0 to 8. However, it's just a shortcut for {0,8}. Given that it's not valid in some Regular Expression implementations and only saves 1 character, it's better to be in the habit of using {0,8}
What you used, {+}, would match one or more { followed by a }.
[ 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, +4 more: wrinklerewindfrance.com/myvigra/ by kol on puzzling.SE (@Mithrandir @micsthepick)
I think that's included, yes -- we have participants from most sites; let someone who is at least vaguely familiar to the site's community represent us
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +2 more: Keto Tone Reviews by Borgh Van on askubuntu.com
[ 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, +4 more: wrinklerewindfrance.com/myvigra/ by AndLaws on puzzling.SE (@Mithrandir @micsthepick)
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, potentially bad keyword in body: maxno extreme australia by vdfdfvbds on askubuntu.com
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, blacklisted website in body, +4 more: reviverxtry.com/lumineri-skin/ by Jiyarezzzz on puzzling.SE (@Mithrandir @micsthepick)
BTW sorry fotr the mixup, I wanted to post them separately and went to past message to copy the question part - by mistake I ended up editing the message.
Using the websocket makes FIRE somewhat more responsive, but there are still some basic issues with some data from the websocket being indeterminate, particularly when there's more than one report for a specific URL. For instance, in the case where there's more than one MS report for a URL, there's no way to know, from just the websocket to which report feedback applies.
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +6 more: healthpurelives.com/keto-tone/ by zivv on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, blacklisted website in body, link at end of body, pattern-matching website in body: Vital Diet Keto by Naja HJzh on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, link following arrow in body, pattern-matching website in body, +1 more: What is Saint Elias? by Saint Elias on superuser.com
@tripleee 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.
