@Lyxal np. Sounds good. If you want to participate more actively, we'd welcome the help. If you do want to, there are more permissions to set up, but we don't want to force those on you. :;
@Lyxal If you want to give feedback, which you're welcome to do, I'll need to flip a few more bits for permissions, but I happy to do so. Feedback to SmokeDetector can be given through chat messages, as you've asked, on metasmoke, or through userscripts. Most of the feedback people give is either through userscripts or on metasmoke, primarily because people find those to be easier.
@Lyxal Yes, it is. Give me a couple/few minutes to get that set up. I'll be adding the "Reviewer" role on metasmoke and giving you permissions for SmokeDetector in here.
@cigien 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.
@Lyxal I've added you to the privilege list for SmokeDetector (SD) here in Charcoal HQ. 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).
As I already mentioned, there's the Introduction to Participating in Charcoal. I mention it again here, so most of this information is all in one group of messages.
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.
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, 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 :)"
@hyper-neutrino The !!/blacklist command has been deprecated. Please use !!/blacklist-website, !!/blacklist-username, !!/blacklist-keyword, or perhaps !!/watch-keyword. Remember to escape dots in URLs using \.
@hyper-neutrino That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
[ 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 keyword in body (388): On the off chance that your knees hurt by Dale Steyn on stackoverflow.com
@Xnero Who pinned a message is noted at the top of the message's history page (linked from the message's popup menu). As to why, you have to ask the person who pinned it, but I think it was a mistake.
@Mast I've unpinned this message. I'm willing to re-pin it, if you really wanted it pinned, but you pinning it feels more like a mistake than intentional.
@rene Yep, at least all the ones which didn't look like they'd cause damage, perhaps most of the ones which didn't look like they would cause unreversible damage, and definitely all the ones I create. :)
@Xnero I was on mobile. I know how the buttons work on PC, yes. On mobile, all kind of weird things happen if you tap in the wrong spot or drag something the wrong way.
CC @rene
If I'd test buttons, I'd do them somewhere else than here ;-)
@cigien User posted 2 answers at the same time linking to their website in a signature. Both were edited to remove the signature, but worth watching domain, and user just in case.
@Mast 'v' is not caught by a blacklist or watchlist item.
Matched by the following regexes: (?:cbd|chill(?:[\W]*+plus)|halo[\W_]*+hair)[\W_]*+gummies on line 2227 of bad_keywords.txt kevin[\W_]*+costner[\W_]*+cbd(?:[\W_]*+(?:buy|gumm(?:y|ie)|oil|review|\d++|[\da-f]{5,}+)s?)* on line 2500 of bad_keywords.txt