Update: Matt, Sorry I made a typo.

[...] for sure if that was the case. Andrew Nacin who is also one of the core developers of WordPress has requested that a proper explanation be given that sets the record [...]

It's Matt Mullenweg not wag!

Update: You made another typo. It's spelled Mullenweg.

I think it would have been better for you to apologize for insinuating early on that this was a WordPress issue, and not setting the story straight. I mean, this blog flat out wrote “this issue is not with our hosting servers” and have repeatedly referred to your situation as a “WordPress issue.” It's not the typo the community is concerned about. It's the ambiguous phrases and factually inaccurate statements that have yet to be properly corrected, which is poor communication at best and dishonest at worst.

Perhaps when NS has finished with the fallout and cleanup for this, this blog will offer a full mea culpa and explain that it *was* your hosting, and was *not* WordPress. That would go a long way.

Sorry ! corrected now – shashi

Sorry Andrew ! Bad habits like typos are hard to break . I think we have been forthright about our communications and giving our customers info as we come across it. We will keep posting updates on this blog.

Shashi

You probably need to go farther and update your post – even write a new one – clarifying that WordPress is not the one at fault for the security lapses recently documented by NS customers. That it was a hosting configuration problem and that the blame does not lie with the software that is hosting millions of blogs for NS and non-NS customers worldwide. Leaving that false implication unaddressed is more irresponsible than a typo.

WordPress has had its own self-induced problems in the past that we have quickly fixed and owned up to. This is not one of them.

Hi Aaron,

Thanks for your comment. I am not even sure that Matt referred to us as far as the debate on WordPress is concerned. Our focus has been communicating with Network Solutions customers and not debating WordPress.

Shashi

Your handling of this is front and center among conversations around this topic in the WP developer world. Regardless of post, it would serve to read between the lines.

Shashi, I love how you've become the NSI scapegoat over the past year or so. Well played sir. One internet for you.

Thats fair. Not sure if we ever said anything about WordPress core. will take feedback about removing ambiguous language to make our messages better

Hello Sashi Bellam Konda (oh, sorry my typo),

I think your sorries must to be pointed to:

- Your clients: for lying about the recent big issue with your servers.
- To WordPress community: for try to wash your hand blaming this software.
- To you: for being a very, very bad boy handling this problem.

Next time make sure knowing what's the issue before point the finger over anybody.

For the rest, good luck with the massive fix in process.

Update : April 14th 2010 Network Solutions does the right thing http://bit.ly/cUrCId

Update : April 14th 2010 Network Solutions does the right thing http://bit.ly/cUrCId

Thanks Ankur. See Update : April 14th 2010 Network Solutions does the right thing http://bit.ly/cUrCId – Shashi

Did you get this resolved ? other wise please send email to listen at network solutions.com

I see. Well done Sashi.

Thank you Dario – Shashi

Hi Mike,

See Network Solutions does the right thing http://bit.ly/cUrCId

Shashi

Thanks Hakre.

Thank you Sriraj garu,

Ikkada choodandi Network Solutions does the right thing http://bit.ly/cUrCId

Shashi

[...] left? Someone who wanted to help customers and some wordpress users who still do not have a clue why their site got hacked and how they can [...]

[...] Network Solutions Blog – Matt, Sorry I Made A Typo [...]

[...] just read it as a name consisting of two words. Well understandable but guess who is complaining in the minute. Do not get me wrong, I do have misspellings all over in my writings as well, but what I strongly [...]