@SmokeDetector While there might be something salvageable there, it's primarily a rant that is much broader than the question. Basically, the amount of editing I'd need to do is beyond what I feel is appropriate to "repair" the post.
I really should take a look at the code and see what it's doing in detail. Well, what I really should do is set up an SD instance so I can play around with it and learn Python.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, potentially bad ns for domain in body, repeated url at end of long post (396): The Good, The Bad and power body by janitahelland on astronomy.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, potentially bad ns for domain in body (393): Whether heterosexual, bisexual by user49381 on rpg.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body, +1 more (492): There are diet strategy strategy tablets by David Lopes on worldbuilding.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body (393): Covee Skin Care Serum by jfvsjxad on apple.SE
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +3 more (596): pilpedia.com/vita-keratin/ by user49381 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): evaherbalist.com/niwali-keto/ by Cetizocu on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, +4 more (690): keto-ultra-diet/ by DanieHawki on apple.SE
While "recently" might not be all that accurate (depends on your POV :-) ), do we really want to have posts reported by SD again at all, if the post has not been edited?
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body (392): Rapid Results Diet Reviews by Enehyak on graphicdesign.SE
@Makyen well, I'd say if the post is older than <insert threshold here>, Smokey should not report it again to MS (that just messes up records there) but it should repost messages, preferably with a STILL ALIVE indicator.
@Glorfindel I starred this because I do like this idea. As a newbie and busy on other things, I visited here from time to time. I'd like to see posts that are already reported, but still there so I can help to flag them. Thanks for the idea, hope to see it implemented soon.
@Glorfindel I don't have a problem with that. OTOH, we could have our userscripts do something which keeps things in front of users. Either way, we would need ways of telling whatever is used that the fact that the post is "alive" should not reported again.
I assume that you mean that most of the SD reports that are displayed in The Fire Department are no longer visible here in CHQ. Hmmm... Your next message sounds like I might have misunderstood. Do you mean that most of the posts reported in The Fire Department have been deleted? If so, then yes, they are. That's largely the point.
@scaaahu Yes, but it's relatively easy to identify which ones are already gone, so you can focus on only those which are still active. That assumes that you can use userscripts in your current location.
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +3 more (492): goldencondor.org/ketozin/ by Keto zin on portuguese.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (790): evaherbalist.com/niwali-keto/ by Cetizocu on drupal.SE
Two examples, just happened. The SO one, It's already gone when I clicked it. The keto one, I was the last one who killed it.
That's why Id like to stay here so I can render more help. There, I just tried everyone and failed. I don't have time to write scripts for that. I am a retied software engineer. I tried not to do any programming work after retirement, too much already.
FIRE helps with flagging faster (except for me, somehow I can't get it to work as quickly as just going to the site itself). But you're right, on work days in the European morning, spam is usually gone 6-8 seconds after being reported (thanks to the autoflags).
@NisseEngström Yes, I understand. That's why I like the idea of "still alive" so I don't have to go thru about 100 lines of more to figure which one I can help.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, potentially bad ns for domain in body (394): hbmbzone com praltrix pills za by jetpent on superuser.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): evaherbalist.com/keto-6x/ by Tommy Gadsden on askubuntu.com
tpu- by Erik the Outgolfer
[ SmokeDetector | MS ] Blacklisted username, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, pattern-matching website in body, +3 more (589): pickwellnessdeal.com/sultra-lift-cream/ by jaserldson on puzzling.SE (@Mithrandir)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, potentially bad keyword in body, potentially bad keyword in title (289): Buy Now Teal Farms Keto by TealFarms on english.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (793): evaherbalist.com/keto-6x/ by user884099 on askubuntu.com
> Pattern-matching website in body, pattern-matching website in title, pattern-matching website in username ---------- Title - Position 4-16: dietblog.com Body - Position 4-16: dietblog.com Username - Position 4-16: dietblog.com
@EriktheOutgolfer 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.
@doppelspooker 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.
@scaaahu I'm sorry to have left this conversation in the middle. Unfortunately, my internet connection cut out just prior to my sending my next message, and stayed down for several hours. As has been mentioned, there are times during the day when we all find it rare to contribute manual flags. The userscripts help in responding faster and identifying which posts are still alive that have tpu feedback and/or autoflags. I'm working on heading them in the direction to make that even clearer.
@iBug Thanks for pointing it out. I'd already changed that in development; just hadn't merged it yet, as it got caught up in some other changes in that area of the code. My expectation is that those should be in the next version.
@SmokeDetector OP is vandalizing their posts in bulk across multiple SE sites. I've custom mod-flagged once on each site, as A) I don't have edit privileges on most of them and a rollback is better than an edit, and B) each site should be checked for posts which they've inappropriately bulk-deleted. For a list of the vandalism detected by SmokeDetector, you can see here.
@SmokeDetector Without the link to fiverr.com, this might be narrowed to be acceptable as a question. With the fiverr.com link, this appears to be just soliciting people to bid on their fiverr gig (i.e. soliciting for off-site assistance/job/contract), which is considered spam.
@quartata The problem is it's not actually blacklisted. The "Bad keyword in title" comes from a special rule in findspam.py that wasn't given it's own reason name. That rule is only applied to titles (and excludes some sites). So, the word was seen in bodies without being detected. Thus, it was put on the watchlist. The watchlist has no direct way to exclude titles. I haven't actually checked which order in time the two detections were added, so it could have been the other way around.
