teward/Osiris: In getting MS post information, recovered from requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Read timed out. (read timeout=10.0)
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (202): Trial balance preparation by kaylawilson on superuser.com (@Ollie)
[ SmokeDetector | MS ] Bad keyword in link text in body, bad keyword in title, link at beginning of body, potentially bad keyword in body, potentially bad keyword in title (209): high class service escorts surat? by priya patel on stackoverflow.com
crazy text from the About section in the spammer's profile: "Surat is the most attractive place for commercial person as well as business men they looks different apportunity for him they want to get new when they fell lassy then they find first independent female service in surat those how can give best female comfort to him. so we grape the opportunity"
[ SmokeDetector | MS ] Blacklisted username, few unique characters in answer, mostly punctuation marks in answer, potentially bad keyword in username, repeating characters in answer (293): How to move list items to the right? by wingding on stackoverflow.com
@tripleee 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 the pattern you entered.
@tripleee 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 the pattern you entered.
metasmoke now defaults to including the current post in the stats for a spam domain, so if you see (1, 0, 0) it often means that the spam you are looking at was flagged as TP
@tripleee The !!/blacklist command has been deprecated. Please use !!/blacklist-website, !!/blacklist-username, !!/blacklist-keyword, or perhaps !!/watch-keyword. Remember to escape dots in URLs using \.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username (196): Web Design Course in Bangalore by a2n academy on askubuntu.com
@tripleee 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 the pattern you entered.
spammers back after Christmas, reminds me of the parable about Usenet as a herd of elephants with a stomach problem
Usenet is like a herd of performing elephants with diarrhea — massive, difficult to redirect, awe-inspiring, entertaining, and a source of mind-boggling amounts of excrement when you least expect it. — Gene Spafford, 1992
@tripleee It was something I repeatedly found to be counter to my expectations when looking at the TP/FP/NAA numbers for domains on posts. I, eventually, deduced that the current post was being removed from the counts, but prior to figuring that out, I went through a period where I felt that I couldn't trust those numbers to be accurate, as they never matched what was found when searching for the domain and were often different from post to post for the same domain.
I much prefer those numbers to be consistent in all places where they are displayed.
The primary reason for the recent change was to speed up display of posts, it just ended up that what needed changing to make that faster was the portion which was calculating the domain total/TP/FP/NAA numbers.
It would be quite easy to have both the increased speed and keep the numbers displayed as they were (just subtract out the current post using the post data we already have, not in the database query), but I'd want there to be a really good reason to display the domain numbers without the current post included. As it was, I found it quite confusing, then frustrating once I figured out what was being done.
It looks like all the CI failures we're seeing are a result of GitHub having intermittent problems. The issues are primarily failures to clone our ChatExchange repository, which is one of the dependencies.
@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 the pattern you entered.
@tripleee 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 the pattern you entered.
@tripleee Already watched on line 31513 of watched_keywords.txt
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, blacklisted website in body, potentially bad asn for hostname in body, potentially bad ip for hostname in body (265): How to Recover Outlook PST File? by PST Recovery on stackoverflow.com
