undo@metasmoke:~$ sudo mysql -u root metasmoke < ms.sql
^CCtrl-C -- query killed. Continuing normally.
^CCtrl-C -- query killed. Continuing normally.
^CCtrl-C -- query killed. Continuing normally.
ERROR 2013 (HY000) at line 2434: Lost connection to MySQL server during query
$ ssh -i EC2KeypairExample.txt ubuntu@3.81.154.25:/home/ubuntu/dump.rdb .
ssh: Could not resolve hostname 3.81.154.25:/home/ubuntu/dump.rdb: Name or service not known
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, link following arrow in body, +4 more (593): How Brilliance SF Works? by brillancsffr on meta.SE
@SmokeDetector It seems to me that "please consider deleting yourself," directed at a specifically named user, qualifies as rude/abusive. Whether it was useful for me to report this to SmokeDetector and what feedback is appropriate I am not sure. (I'm not saying this to disagree with the naa feedback given thus far, just to explain what I was thinking in reporting it.)
@SmokeDetector While this is definitely NAA, the edit which produced this version was specifically, and only, adding a moderately rude response to a comment on the answer. Given that it was an edit that added this rude portion, it would be considered TP, as we would want to block the edit.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, body starts with title and ends in url, potentially bad ip for hostname in body, +3 more (392): up2health.com/slimphoria-keto/ by DonaMiller on apple.SE
I'm having a problem where http:// URLs don't work. https:// URLs do work. The http:// URLs should, and usually have, redirected to https://, but that appears not to be working at all.
@EliahKagan For example, when I first wrote this message, I copied the URL from a SmokeDetector message. It didn't get me to the page. I manually added the s and it did (and I edited the message and my MS feedback so the working URL would be used). I don't think this has happened before though.
If you have a problem with metasmoke, please open an issue on GitHub. We switched over to the new server for MS a few hours ago. So far, it's working well. However, there are going to be some things broken. We need to make note of them so they can be fixed.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +3 more (590): Keto Tone France by cadsyuzt on graphicdesign.SE
Regarding http:// redirection, I think the intended behavior is for them to redirect to the corresponding https:// URL and that this worked before. But the main practical problem, I think, is that some links to metasmoke that SmokeDetector posts in chat are http:// links. Specifically, the "feedback received" links with "[MS]" at the end are http://. Perhaps that should itself be regarded as a bug in SmokeDetector.
But even if that is changed in SmokeDetector, there will still be old http:// link to metasmoke in chat and in feedback that people copied from SmokeDetector's chat messages.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad keyword in body (293): Supplement Rise by JosephJMabry on askubuntu.com
@EliahKagan 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 body, bad keyword in title, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, +2 more (297): Where To Buy Viaxxl Male Enhancement? by JasonMury on graphicdesign.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, +5 more (886): Empowered Boost Male Enhancement by Adamlson on superuser.com
