[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in URL, link following arrow in body, pattern-matching website in body, potentially bad NS for domain in body: Keto Fit And sometimes the cure's worse by user123122 on graphicdesign.SE
@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.
[ SmokeDetector | MS ] Blacklisted website in body, link at end of body, pattern-matching website in body, title starts and ends with a forward slash: /keto-fit-diet/ by EvelynNorton on drupal.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body: Keto Fit Diet weight loss by LaureJones on drupal.SE
@Mithrandir eeeehh. Admins can change any status, but I'm not sure it's a good idea to open that up more. Someone needs to be able to edit anything, but in general only the person who created the report is going to know about status changes.
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-8: XexLift Body - Position 1-8: XexLift Username - Position 1-8: XexLift
@ArtOfCode I've done that. Let me know if there were any mistakes in my commits, and I'll fix them up. CI seems to be taking it's time, so I've triggered a rebuild. Surprisingly, Robocop passed first go.
before_action :verify_admin, only: destroy is valid syntax, right? Equivalent to only => :destroy?
okay, Wordpress chat got back to me. @tripleee they said that perhaps your tickets weren't processed because they were sent by email not the on-site form. I'm going through and using the on-site process now
[ SmokeDetector ] SmokeDetector started at [rev c07f9f0 (SmokeDetector: Auto unwatch of ^(?!user)[a-z]{4,6}19[0-9]{2}$ by Mithrandir --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/c07f9f0) (running on teward/Solar Flare)
[ SmokeDetector ] SmokeDetector started in standby mode at [rev c07f9f0 (SmokeDetector: Auto unwatch of ^(?!user)[a-z]{4,6}19[0-9]{2}$ by Mithrandir --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/c07f9f0) (running on teward/Solar Flare)
@SmokeDetector It's Software Recs. The question is basically asking for this type of information. Although, I'm not sure that saying please contact us for as yet unreleased software is a legit answer on that site.
We don't have such a blacklist criteria. While it might be reasonable to blacklist it, if we are going to be using such criteria on a regular basis, which people have progressively been doing more and more, then we should document what our blacklist requirements really are, rather than break the current guidelines several times a day.
For something that is part of an Ongoing Campaign, where Ongoing Campaign is defined as something directly associated with a campaign that already has something that qualified for the blacklist using the normal criteria. While this might qualify, it's not clear to me that this is actually associated with the others. There are some that are similar, but use text that is sufficiently different such that I really don't consider them the same campaign.
Perhaps the issue is that I use a stricter definition of "substantially similar to a number of other recent spam posts".
To be clear, I'm not saying that this particular domain shouldn't be blacklisted, just that we, or at least I, should have a clearer understanding of what we mean by "Ongoing Campaign".
> Url in title, blacklisted website in body, blacklisted website in title ---------- Title - Position 8-21: hacklike.mobi Title - Position 1-21: http://hacklike.mobi Body - Position 8-21: hacklike.mobi
@bertieb It was re-scanned when the question was edited. Unfortunately, SD doesn't actually prevent re-reporting the same post (even when it hasn't changed), except for a relatively brief time-window, which is extended by providing ignore feedback, but that's only effective on a per-instance basis.
