It seems we are not allowed now to question moderators. See https://meta.stackexchange.com/questions/42754/why-was-this-meta-question-closed-as-a-duplicate

And yes Jeff, I fully expect to be put in the sin bin for this, and maybe on SO too. Some of us believe in open expression in both code, documentation, use and support, and believe that suppressing this in any form is wrong. You seem to disagree. OK, but consider that the people like me providing free and open answerers on your site is what makes it work.

  • 3
    This should be very entertaining... – Tyler Carter Mar 19 '10 at 1:57
  • Looks like you are not in good mood today, +1 – YOU Mar 19 '10 at 1:57
  • Just wait for them to think up a new policy that targets you specifically but fluffs in other users to make it seem not so direct. – random Mar 19 '10 at 2:00

When have we ever allowed attacking other users? Whether it's a moderator or not is irrelevant; if someone started a thread titled "I think Neil Butterworth is a terrible user!" I would edit it in the exact same way.

Concentrate on the specific posts you have issues with. "Why was this question closed?" is a totally reasonable meta question. "Why does {user x} suck so much?" is not.

  • 8
    +1 for I would edit it in the exact same way. – YOU Mar 19 '10 at 2:00
  • I knew this was going to be entertaining... – Tyler Carter Mar 19 '10 at 2:05
  • 2
    Having just read through all the links in this 'saga' I have come to a conclusion - some people take this thing WAY to seriously. It's just a few votes, and besides - criticizing users is not the way to win people to your side. (I'm of course referring to Neil) – uɐɯsO uɐɥʇɐN Mar 19 '10 at 2:09
  • 3
    Also, you're definitely allowed to questions us. The moderator you're complaining about explicitly requested that you do. meta.stackexchange.com/questions/39405/… – Bill the Lizard Mar 19 '10 at 2:10
  • 1
    Questioning is good. Criticizing people - not so good. Insulting, well that's just plain bad. – uɐɯsO uɐɥʇɐN Mar 19 '10 at 2:14
  • @Bill Which I've already pointed out .. several times during the saga: meta.stackexchange.com/questions/42754/… – Tyler Carter Mar 19 '10 at 2:14

If you want to question a moderator, email them. Most of them have contact information somewhere.

If you want to complain about the actions of a moderator, email team@stackoverflow.com. Jeff loves email.

And if you want others to commiserate with you on Meta, be subtle... For some reason, folks are much more likely to agree when you don't actually name names.

  • 3
    lol @ Jeff loves email – juan Mar 19 '10 at 2:13
  • Sorry, doesn't "locked" mean you can't add to the question/answers? Apparently not. So what does it mean? – nb69307 Mar 19 '10 at 2:15
  • @Neil, Only 'closed' prevents additional answers. – Tyler Carter Mar 19 '10 at 2:16
  • @Chacha: that used to be the case, but it changed because apparently that confused people - now locking also prevents new answers... @Neil: ...however, there's a hefty grace period that lets you cram in answers after locking (and actually, I suspect there might be another bug involved here... edge cases like this tend to get ignored) – Shog9 Mar 19 '10 at 2:18
  • @Chacha: meta.stackexchange.com/questions/13059/… I guess 10k's can still add answers. Edit: or maybe Shog was in the process of typing just after the lock. – Jon Seigel Mar 19 '10 at 2:18
  • Oh arse. I think Jeff's meaning was obvious, whatever the technicalities - discussion over. – nb69307 Mar 19 '10 at 2:21
  • the meaning of locked was recently changed to also mean no new answers can be added. Sorry for the confusion; it probably always should have behaved that way. – Jeff Atwood Mar 19 '10 at 2:37
  • 1
    @Jeff So I don't get to make a reply as an answer? Why am I not surprised? – nb69307 Mar 19 '10 at 2:41
  • I tried to post a comment for the question but there was no grace period... – uɐɯsO uɐɥʇɐN Mar 19 '10 at 2:53

You must log in to answer this question.