Comment by kn0thing on 02/07/2015 at 21:19 UTC

-877 upvotes, 5 direct replies (showing 5)

View submission: /r/IAmA set to private over mod firing

View parent comment

We're still handling this -- please direct emails to AMA@reddit.com -- and are in touch with the scheduled AMAs across the platform.

Replies

Comment by Lord_Vargo-Hoat at 02/07/2015 at 21:30 UTC

241 upvotes, 1 direct replies

Pretty sure that you aren't handling this, by letting go of the employee who does handle this. The issue now is what everyone's going to do now that you aren't handling this.

It's a bit like knocking over someone's vase, then standing in position over it shouting "I can save it! I can save it!" Well, no. You already broke it. The only options now are to replace it or trash it.

Comment by [deleted] at 02/07/2015 at 21:42 UTC

16 upvotes, 0 direct replies

Normally you don't replace competent and well-liked employees with a group of inept dolts.

But I guess that's the reddit way.

Comment by [deleted] at 02/07/2015 at 21:46 UTC

15 upvotes, 0 direct replies

Holy shit you guys fucked up today:

1. Search function is a disaster, *after* the mods warned you about it.

2. Letting go of an employee is your business, perhaps the reason was legitimate too. Don't care. But the lack of any communication whatsoever towards the moderators not only shows massive disrespect towards the mods but towards the entire userbase.

Get your shit together please, you're entering "every man is responsible for his own soul' bullshit territory again.

Comment by asperatology at 02/07/2015 at 21:31 UTC

7 upvotes, 1 direct replies

How many employees are there currently handling this? Just wondering the size of your team.

Comment by [deleted] at 03/07/2015 at 08:03 UTC

1 upvotes, 0 direct replies

Cool. Seriously though, and i know you were as blindsided as we were (probably) but please transition this better. Having it thrown at us out of the blue was, well, shit. Not yelling at you but at the situation.