@Stormblessed You have to join the Stack Exchange Charcoal Team. You're welcome to do so. I'll need to check on what the process is at this point. What did that link say when you tried it?
See here in the Charcoal HQ transcript:
scaaahu
What does " Luncheon meat detected" generally mean? Spam? R/A? or just suspicious? or something else? This was my misunderstandings from.
Robert Longson
The intent is to catch "hashes" left at the end of the post. It'...
@Stormblessed In general, the policy is that information on the Charcoal Team should not be shared (particularly relating to detections and some other details). The reason for that is that it the Team has been used to communicate information which we don't want spammers to have, and some spammers are known to read this chat and/or Meta.
The past policy was that information about that specific detection was not being shared in any detail. That detection was to detect a specific prolific spammer, who was known to read this chat room and Meta. Thus, we were not generally sharing information about that specific detection. However, enough people have asked about it such that most of the information is probably out there, but I wouldn't be comfortable giving the detail in the Team post.
Ironically, the spammer could just look in the SmokeDetector source code to figure it out, but the point was trying not to make it easy for them. However, that spammer hasn't been around for months, and may change what they do/post, if they return.
@Stormblessed We'll see who answers your Teams/Channel question. I'm interested to see what other people's opinions are.
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more (691): mumybear.org/keto-6x/ by vpwc on askubuntu.com
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +6 more (693): awaretalks.com/keto-gx800/ by TeriesaMulins on askubuntu.com
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, body starts with title and ends in url, potentially bad ns for domain in body, +4 more (492): pil4pedia.com/keto-6x/ by livalauri on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, link following arrow in body, +3 more (687): This way, you can research each by elmabelsr on superuser.com
Warning: teward/Supergate: 10 latest connections to metasmoke have failed. Disabling metasmoke
@Makyen Yep just about 24 hours, possibly closer to 25 hours ago.
@Undo We're having very similar issues with MS as we had 24 hours ago (i.e. "Redis::TimeoutError in ..." and the various slow/intermittent issues). It could use a kick, but I don't think you're around. cc @ArtOfCode @thesecretmaster
@Makyen That pattern looks like it's already caught by Bad keyword in body, Pattern-matching website in body, Pattern-matching website in answer, and Bad keyword in answer; append -force if you really want to do that.
Bad keyword in body - Positions 27-42, 875-890, 948-963: maleenhancement, Position 436-452: Male Enhancement, Position 644-662: sexual coexistence, Positions 1027-1043, 1107-1123: male-enhancement Body starts with title and ends in url - Body starts with title and ends in URL: https://supplementscan.com/velofel-male-enhancement/ Pattern-matching product name in body - Position 436-452: Male Enhancement, Positions 1027-1043, 1107-1123: male-enhancement Pattern-matching website in body - Positions 20-52, 868-900: velofelmaleenhancement.wordpress, Position 1000-1018: supplementscan.com
@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 Bad keyword in body, Pattern-matching website in body, Pattern-matching website in answer, and Bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, pattern-matching product name in body, potentially bad ns for domain in body, +3 more (394): Lean Boost Keto www.fireupchips.org/ by Chice mems on academia.SE
@Undo cc: @ArtOfCode @thesecretmaster Looks like MS resolved the problem. I also rebooted MS, yet again, at that time, so it's not clear if yet another reboot helped, or if MS was resolving the issue after ~1 hour and the reboot was coincidentally timed, or if the resolution required a reboot to finish resolving the issue.
@Makyen That pattern looks like it's already caught by Blacklisted website in answer, Bad keyword in body, Blacklisted website in body, Potentially bad keyword in body, Potentially bad keyword in answer, and Bad keyword 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 answer and Potentially bad keyword in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Blacklisted website in answer, Bad keyword in body, Blacklisted website in body, Potentially bad keyword in body, Potentially bad keyword in answer, and Bad keyword 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 answer and Potentially bad keyword in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Blacklisted website in answer, Bad keyword in body, Blacklisted website in body, Potentially bad keyword in body, Potentially bad keyword in answer, and Bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Blacklisted website in answer, Bad keyword in body, Blacklisted website in body, Potentially bad keyword in body, Potentially bad keyword in answer, and Bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; append -force if you really want to do that.
> Blacklisted website in body, blacklisted website in title ---------- Blacklisted website in body - Position 2-16: strikingly.com Blacklisted website in title - Position 2-16: strikingly.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (296): Keto Vatru!! Reviews & Cost by sisiziiz on drupal.SE
@Makyen That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; append -force if you really want to do that.
@double-beep That pattern looks like it's already caught by Bad ip for hostname in answer and Bad ip for hostname in body; append -force if you really want to do that.
@Makyen 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.
@Makyen That pattern looks like it's already caught by Mostly punctuation marks in answer and Mostly punctuation marks in body; append -force if you really want to do that.
@Makyen 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 ] Blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, potentially bad ns for domain in body, +2 more (396): Source Organics Keto We genuinely by mickyhaissy on askubuntu.com
@Shree 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, body starts with title and ends in url, link at end of body, pattern-matching website in body, potentially bad asn for hostname in body, +1 more (392): Encounters sex-associated problems like by uzofudu on askubuntu.com
@double-beep That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
See here in the Charcoal HQ transcript:
scaaahu
What does " Luncheon meat detected" generally mean? Spam? R/A? or just suspicious? or something else? This was my misunderstandings from.
Robert Longson
The intent is to catch "hashes" left at the end of the post. It'...
