RolStoppable said:
It's part of the moderators' job to talk to the community. Everyone should know this when they apply for a mod position. Your defense for mods isn't really a defense, but rather makes them look bad if that were how they think about things.
Second paragraph: As soon as a moderator says that a decision wasn't solely his, it could already be considered passing the blame.
curl's moderation got overturned, but starcraft isn't taking flak for that. Not from me anyways.
|
It is part of a moderator's job to talk to the community. And as Ka-Pi pointed out, we've been doing just that. Cone has now entered the thread and decided to reveal I consulted with him on Curl's ban. I appreciate him doing that, but also feel he should not have too.
Whether or not I cop flak is immaterial to the base point here. Irrespective of who I consult with, when I make a ban, I am responsible for that ban - my name tag goes on the ticket. When I reverse a ban, I am responsible for that as well. In this case as Cone points out, we lacked context, and that meant I wound up making the wrong call. When a third mod brought this to my attention and asked me to take a second look, I did a quick Google search, confirmed that mods suspicions, unbanned Curl and sent a quick note to explain and apologise.
So given that, why is it important that I consulted with another mod in the first instance? Just because ultimately one moderator takes responsibility for a ban, doesn't mean they shouldn't do everything they can to get it right, and to be consistent with the rest of the team. In this case, that didn't work. In the overwhelming majority of cases (several moderations both small and severe a day across the mod team), that system works well to ensure there are no overreactions, and everyone is treated fairly.
In a nutshell - Curl got banned because Cone and I didn't know a bit of gaming trivia that is now 4-5 years old. That ban was very quickly reversed once our error was realized.