@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 Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, pattern-matching product name in body, pattern-matching website in body, +5 more (598): walgreensdiet.com/keto-pure-canada/ by insestilrow on askubuntu.com
Looks like it was added as a watch in October '18, and removed a few days thereafter. It's currently detected by both "Potentially bad asn for hostname in {}" and "Potentially problematic ns configuration in {}". We could easily exclude it from the ASN detection.
[ 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 asn for hostname in body, +2 more (396): Prime Time Boost by mattewfaison on askubuntu.com
@Makyen 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.
@NisseEngström ...that's weird, for a moment there, my profile wasn't showing up any flags. Anyway, seems to be working now. My flag was marked as helpful, and Makyen's comment seems to give a good description of what happened.
@ArtOfCode do you know where I can find the most up-to-date diagram for all of Charcoal's systems? I've found this one, but it has duplicate HTTP arrows from Smokey to chat, so I think it might be an older version
@tripleee 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.
> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - everfreshkitchen.com NS suspicious ns59.domaincontrol.com.,ns60.domaincontrol.com. Potentially bad ns for domain in title - everfreshkitchen.com NS suspicious ns59.domaincontrol.com.,ns60.domaincontrol.com.
I'm receiving PCIe bus errors in kern.log of version 16, 18 and 19 of Ubuntu when booting the system:
kernel: [ 13.231617] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
kernel: [ 13.231627] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e0(R...
@tripleee 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.
@tripleee It's two completely different user IDs, not just a name change. The link to the user in the report goes to a "page not found" page, indicating a deleted user.
@SmokeDetector While this is effectively spam, it's mitigated a bit by the fact that an image sourced from their website by a different user was the subject of the question, and the question OP stated that the question OP left a comment on that site's blog about the question.
@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 Bad ns for domain in answer, Pattern-matching website in body, Pattern-matching website in answer, Bad keyword in answer, Bad keyword in body, and Bad ns for domain in body; append -force if you really want to do that.
@tripleee 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 ] Bad keyword in body, link at end of body, link following arrow in body, pattern-matching product name in body, potentially bad ns for domain in body, +3 more (495): How To Use Just Keto? by justketodiet on meta.SE
@tripleee 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.
@tripleee 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.
@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.
I'm receiving PCIe bus errors in kern.log of version 16, 18 and 19 of Ubuntu when booting the system:
kernel: [ 13.231617] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
kernel: [ 13.231627] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e0(R...
