News for hackers. Stuff that matters.
Re:Namecheap disabled imgur.com for abuse by tamar on Sunday February 24, 2013 @08:44PM (#5276841)
I'm Namecheap's Social Media Manager and just want to be clear that the issue here stemmed from trying to contact Imgur regarding child pornography. We made 6 separate attempts to contact Imgur before the domain was disabled. We do admit that perhaps we should have been more aggressive in contacting Imgur , and this is a matter being looked into by our CEO, who added the following to the Imgur update:

"I'm the CEO of Namecheap here. Just want to let you all know that I am personaly looking into this. The domain was taken down by an overzealous abuse team member who had no knowledge of who imgur was. Although we did send 6 seperate emails over the last week, it should have still been escalated. I am reviewing our policy to see how we can avoid this type of situation further in the future. To the folks at IMGUR, I want to sincerely apologize for this situation and the extreme inconvenience this has caused you. If you can connect me with someone in your company. I'd like to give you a personal call and discuss the matter further."

We know that these incidents are unfortunate but are learning experiences for everyone involved. We hope that those of you who are using Namecheap continue to do so and let us work to make the experience a better one for everyone, and we hope that those of you who have not yet used Namecheap don't let this one incident from keeping you away from us. As you can see, we are doing whatever we can to make it right. Hope you can (continue to) give us a chance.

Re:Namecheap disabled imgur.com for abuse by thirsteh on Sunday February 24, 2013 @08:58PM (#5276879)
R.I.P. abuse team member
Re:Namecheap disabled imgur.com for abuse by rebelde on Sunday February 24, 2013 @11:13PM (#5277273)
You have my phone number. Can I expect a phone call before you do something like this to my domain? I don't think it is too much to ask.
Re:Namecheap disabled imgur.com for abuse by tamar on Monday February 25, 2013 @08:27AM (#5278852)
We're revising internal policies so that this doesn't happen again.