@EliahKagan 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.
@Shree 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.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, 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 Pattern-matching website in body, Bad ns for domain in answer, Bad ns for domain in body, and Pattern-matching website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +2 more (491): Slim Phoria Keto by echofrndly on graphicdesign.SE
@JustinKrejcha 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.
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 & 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 "Use my account to cast flags automatically" 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."
@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 Unfortunately, it's not possible through just CSS. That one's using an <input list="tag_list"> and <datalist id="tag_list">, so custom formatting isn't available. We'd need to change the control that's generated. I'll look at it a bit further. It's unusual to be using two different controls for what's basically the same thing.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, potentially bad keyword in body, potentially bad keyword in title (295): Silver Note Keto by Benniollon on superuser.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +3 more (591): SBX Male Enhancement by Mareevesrow on graphicdesign.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +3 more (495): SilverNote Keto by dafegrun on graphicdesign.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +3 more (495): Glamour Skin Cream: What A Mistake! by donalshafer on askubuntu.com
@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.
[ SmokeDetector | MS ] Url-only title, bad pattern in url body, blacklisted website in body, blacklisted website in title, potentially bad ip for hostname in body, +3 more (394): superfastketopills.com/okowatt-reviews/ by EricMcy on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, link at end of body, pattern-matching website in body, +4 more (492): biorexin male enhancement by snekif on drupal.SE
@EliahKagan 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.
