@RyanM They are, actually, "anybody" flags, but the list which is attempted in order (once the order of each sub-list is randomized) has the non-Core users in front, prior to the Core users. This results in the Core users being used for those flag(s) if, and only if, there are not enough non-core users available who both have matching flagging conditions and who are able to flag.
@RyanM but then OP didn't fix it, they just added .com to the vandalism...
weird...
Also the user who vandalised may have been hacked, I can't see when their profile changed but it definitely seems inconsistent with their other posts...
@SmokeDetector custom flagged: For some reason, the question asker seems to have vandalized this user's (admittedly unnecessarily yelly) answer that originally had an actual answer to just say "Noooooooooooooooooooooooooooooooooooooooooooooooo". Please consider a warning and/or suspension for this abuse of the edit privilege.
Blacklisting users can be done by any privileged user (at least any reviewer, not sure if it's actually anyone at all); blacklist privilege only applies to changing the regex watchlists/blacklists
Separately, the rmblu command doesn't actually check if the user was on the blacklist in the first place:
@cigien actually, as I discovered, you can give that feedback from MS if you cast a spam or abusive flag, regardless of whether the flag actually gets cast (it can't if you don't have an account on the relevant site)
@Nick Hmm, I assume you're referring to the buttons above "Create Abuse Report"? For some reason, I don't recall seeing those before. Are they new features, by any chance?
@Nick Oh, right, that's a Core privilege. And yeah, they're text; I just call them buttons, since I can click them, but that may not be the right terminology.
@Nick 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.
@Yatin I am aware of 48 blacklist managers. Currently in this room: Mast, Makyen, Ryan M, DavidPostill, John Dvorak, Nisse Engström, ArtOfCode. Not currently in this room: iBug, Jeff Schaller, doppelgreener, WELZ, rene, CalvT, Cody Gray, A J, a spaghetto, NobodyNada, Thomas Ward, Ferrybig, angussidney, K.Dᴀᴠɪs, Suraj Rao, tripleee, Zoe, Mithical, Ashish Ahuja, user308386, Shree, Spevacus, Erik the Outgolfer, micsthepick, Byte Commander, Eliah Kagan, paper1111, ProgramFOX, Das_Geek, Henders, double-beep, Tetsuya Yamamoto, Andy, bertieb, bwDraco, Undo, Glorfindel, thesecretmaster, Machavity, Kyll, cigien.
@Nick 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.
> On my next account here, i promise you, i will ask the question you like and not those that i have. I will do everything you like and i dislike, i promise.
Until then i will do some programming on my own, and i will come for help one step before i create the next facebook, i swear.
@Mast True. I left a comment under the answer. They're active, so they may fix it. There's still a lot of answers, so I feel better flagging it just in case.
