@Vickel 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 word(s) if you really want to add the pattern you provided.
@Vickel IIRC the blacklist criteria includes 5 tp; mobile now so I don't have a handy link to it
Sometimes during high activity (where more flaggable posts are expected), I've seen preemptive blacklisting. Personally, I keep half an eye on those numbers - just like you did - and add a blacklist entry if/when it hits 5.
@user16217248 The regex is with[\W_]*in[\W_]*(?:24|twenty[\W_]*four)[\W_]*hours, which on MS has results of 409 Total / 296 TP (72.37% TP) / 103 FP / 0 NAA. It was added a bit over a year ago on 2022-05-05. Since then it's seen 137 TP and 75 FP for 64.6% TP. However, the vast majority of the TP were for Support Number spam, but that text (mostly) stopped being used after a month, or so. Since then, approximately 2022-06-10, there have only been 27 TP with 62 FP, for 30.3% TP. Within those 27 TP, 4 were detected only by this watch entry or entries which were created from posts which this entry detected.
@user16217248 BTW: Please don't run more than 2 regex searches at a time. Regex searches tend to be compute resource intensive, and it's helpful to others for one person not to be running a lot of them in parallel. If you search for the wrong thing, leave the tab open so you know when it's complete. Closing the tab doesn't stop the search process on the server.
@user16217248 You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
@user16217248 You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
@user16217248 I've added you to the privilege list for SmokeDetector (SD) here in Charcoal HQ, which also applies to several other rooms. You should run the !!/amiprivileged command to verify. It would be a good idea to read through the Feedback Guidance, SmokeDetector wiki, and SmokeDetector commands (in particular feedback).
If you haven't already read it, there's an Introduction to Participating in Charcoal. You may have already seen that introduction and some of the other things linked here, but this wall of text puts several of them in one place.
You may also want to look at the userscripts we have available (GitHub), as they can be quite helpful, depending on how you want to participate. For viewing, feedback, and flagging in chat, I find FIRE and AIM to be the ones I use the most. I also find SIM (install) convenient.
For flagging through the userscripts, your metasmoke account needs to be write authenticated with SE, which, if you haven't already done so, can be done from the authentication page and doesn't require you to also sign up for autoflagging, although authenticating is also a required step for signing up for autoflagging.
In addition, to enable manual flagging through the userscripts, the checkbox that says "Allow metasmoke to raise flags for my account" on this page also needs to be checked. If you have no entries in the "ID Site Count Flags Used Today" list at the bottom of that page, then autoflagging will still not be enabled, but manual flagging through the userscripts will be enabled.
Just so you know, we normally tell people when they are getting privileges that we practice the "ton of bricks" discipline method here: If you mess-up sufficiently, or consistently, we come down like a ton of bricks :-).
To quote ArtOfCode: "TL;DR: ton-of-bricks is mostly to say that we almost never need to enforce things because things enforce themselves through having a good community here. If it gets to the point that someone's enforcing something, something's gone badly wrong."
Quoting NobodyNada [with a bit added]: "Note that 'mess up' doesn't mean 'make a mistake', it means 'do something intentionally irresponsible/antagonistic' [or consistently do something wrong and not change when it's, repeatedly, pointed out]. Charcoalers are generally quite friendly, forgiving of mistakes, and willing to help each other learn. We recognize that our systems and policies have quite the learning curve -- so don't be afraid of us :)"
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title (3): Là Gì Xổ số Việt Nam by 嘿哈哈 on ethereum.SE
@user16217248 It looks like the majority of time is spent getting the count of remaining reviews and, depending on the domains contained within the post, the TP/FP/NAA counts for the domains.
@user16217248 The preview is generated by JavaScript from the Text view. I haven't noticed that it's slow. Most posts aren't all that complicated, so shouldn't take much processing or rendering. Can you link to an example review or post? The speed of that render should be the same for the post in review and the post page. Which OS/browser are you using?
@user16217248 OK. A link to an example review or post where you found it to be slow would be helpful. I haven't experienced any slowness (win10/Firefox) rendering the preview which I'd identified as unexpectedly significant.
@user16217248 I don't see that one as blank. OTOH, a few moments earlier I did experience a different one as blank. I'll see if I can duplicate the issue.
@user16217248 Hmm. IIRC it will ask for a token (eight ish chars I think), and then you copy that into FIRE, that works for me, with SE login. Did it have you do that?
That must be checked for flagging in FIRE to work, but the warning is important, and note that I believe your flags may be used in spam waves despite what it says (someone else can confirm that, though)
^ This appeared in an answer that did have a proper disclaimer, thus wasn't technically spam, but it was also from a brand-new user, so I don't want it becoming an epidemic without someone noticing. That post wasn't caught. I already converted it to a comment, so I don't want to undelete, report, and re-delete it.
@user16217248 The issue of the preview not rendering should be resolved. You'll need to reload the page to get the new JavaScript, not just navigate to a new page on the site, as that doesn't actually reload everything. Please tell me if you still experience a problem.
@Makyen Agreed. I've written up some possible wording for a note about that in a PR on GH, but note that I haven't yet tested this change (and I marked it as a Draft PR so it can't be merged yet). Also... do we have a place where we define spam waves? It might be worthwhile to link to said place, but I couldn't find anywhere that spam waves are explained (I know what they are, but I meant in documentation)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +3 more (487): Juzfit ACV Keto Gummies by loisrpitts on askubuntu.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (3): Photo editing app iOS by suresh r on stackoverflow.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, bad keyword in body, blacklisted website in body, link following arrow in body, +2 more (484): How to upload MBOX to Outlook? by Joe Binter on superuser.com
[ SmokeDetector | MS ] Link at end of answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (136): get data between start date and end date by Microseiche on stackoverflow.com
