@Undo @ArtOfCode @tripleee @iBug Currently we have no SD instance running. This could be resolved quite a bit faster by someone that's familiar with ChatExchange, SmokeDetector, or at least Python. This appears to be a couple of problems. Most of the time, SD fails to log into SE through ChatExchange. If let to sit for a while, it will log in (see above) and actually send something to chat, if it is started in standby mode.
If it is not started in standby, then it appears to fail when attempting to connect to the WebSocket. It also fails to connect to the WebSocket when moving from standby to active. When it's active, it will then go into a reset loop trying to login to SE and failing.
The WebSocket issue produces the following output:
[02:23:50.624] Configuration loaded from "config"
[02:23:50.629] GlobalVars loaded
[02:23:50.876] Global blacklists loaded
[02:23:51.635] ChatExchange username loaded from config
[02:23:51.635] ChatExchange password loaded from config
[02:23:52.653] Logged in using cached cookies
/home/ec2-user/SmokeDetector/chatcommunicate.py:139: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read msg.pyyaml.org/load for full details.
room_dict = yaml.load(room_config.read())
SD is not accepting chat commands/feedback/etc. on my instance. If another instance comes up, ping me so I can stop mine and re-enable commands. Currently, there appears to be an issue with the chat WebSocket on SE's side. I had to disable listening for commands in order to get SD to not crash.
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +6 more (792): nutritionless.com/vita-health/ by cwwovseq on drupal.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +7 more (891): nutritionless.com/vita-health/ by cwwovseq on askubuntu.com
@SmokeDetector This is the 3rd answer by this user which is at least very similar and describing their software. As indicated by tripleee's message above, the user has been directed to the promotion policy. While they are disclosing that they wrote it, it's getting to the point where I'll be considering it excessive promotion.
In case it's not clear, comments like my previous message ^ won't be automatically forwarded to MS as an MS comment. You will need to manually place them as comments on MS.
[ 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): But it will become very vital to therapy by fuhewiai on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, link at end of body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (295): Keto XCG Review : Price, Side Effects by LucileHolt on meta.SE
[ 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, +3 more (591): Keto Black Canada by JeanPufer on askubuntu.com
@double-beep 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.
@double-beep In general, I consider it better not to combine these, in most cases. If the content continues to be spammed, then they will be moved to separate blacklists. A.1) When that happens, the person doing it will most likely not be thinking about how you happened to combine it (they should, but it's clear we sometimes forget to do so). This can result in duplicates on the watch and blacklist due to people assuming the watchlist entry is automatically removed.
A.2) if one qualifies for blacklisting prior to the other, then the user adding that one to the blacklist has to deconstruct the regex to split them up, rather than have the appropriate entry automatically removed.
B) Under most circumstances, the machine compilation of the overall regex will negate any savings which is obtained by manually combining two of the almost 10,000 entries. That doesn't mean that you shouldn't think about what the regexes are asking the regex engine to do, just that optimizing two to use fewer text characters isn't all that beneficial.
there is no direct support for that; where would they go? however you can use regex comments, like !!/watch test_regex(?#comment is included but ignored)
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in username, blacklisted website in answer, potentially bad keyword in answer, username similar to website in answer (326): Which VMware API should I use? by Braindumps4IT on stackoverflow.com
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (295): There is a, truth be told, silly prevalent by ghjdfh on puzzling.SE (@Mithrandir)
I was wondering if keto keyword can be blacklisted and be excluded from some specific sites (e.g. Chemistry, Medical Sciences and where we get FPs), so that the blacklist won't be full of keto, keto, keto and keto.
@double-beep it could be done via a custom rule but I would just live with it ... perhaps instead remove the watch and reimplement that as a custom rule which excludes the sites where we get mainly FPs?
if you want to give it a shot, notice the odd interaction between sites and all_sites(if I remember these keywords correctly)
Check Your Privilege The page you're trying to visit requires more privileges. You need to have the Reviewer role to view this page. You currently have the following roles: Reviewer, Flagger, and Core. If you think this is an error, tell an admin.
@double-beep 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.
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body (395): provides you with a slim and trim body by StellaDenston on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, potentially bad ip for hostname in body, +3 more (494): Where to buy Garcinia 360 Slim Reviews? by jessi jess on askubuntu.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ip for hostname in title, bad keyword in body, body starts with title and ends in url, pattern-matching product name in body, +6 more (593): factsofsupplements.com/slim-tone-australia/ by kasashi on graphicdesign.SE
@tripleee That pattern looks like it's already caught by Pattern-matching website in answer, Bad ip for hostname in answer, Bad ip for hostname in body, and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +2 more (590): The body muscle power Cover Up by janabfelix on arduino.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body (197): Trash icon error by Etoblack689 on askubuntu.com
@double-beep 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.
PR#2912 ("double-beep: Watch f2fdiet\.com") opened by SmokeDetector
@double-beep That pattern looks like it's already caught by Blacklisted website in body, Potentially bad keyword in answer, Blacklisted website in answer, and Potentially bad keyword in body; append -force if you really want to do that.
PR#2913 ("double-beep: Watch momentrim-keto\.strikingly\.com") opened by SmokeDetector
@double-beep 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.
