Disgruntled employee kills JournalSpace with data wipe

If you read the original post, the supposed "disgruntled employee" worked for lagomorphics, not JournalSpace, and there's no evidence said employee was involved in the data loss, just conjecture by JournalSpace.<p>Flagged for being incorrect and not adding anything.

There don't seem to be new facts in this article, but it discards the "catastrophic OS flaw" theory and selects the "disgruntled employee" theory though it appears to conflate it with a historical disgruntled employee. It seems this is possibly shoddy reporting rather than new information.<p>Back at journalspace, I notice that if you buy their domain names they will throw in 6 months of free hosting on the same machines that destroyed their business. How generous.

The original journalspace announcement was discussed here, btw: <a href="http://news.ycombinator.com/item?id=417762" rel="nofollow">http://news.ycombinator.com/item?id=417762</a>

If true, the disgruntled employee belongs in jail.

I don't understand -- they seem to have been hosted by someone else; did the hosts not do backups or did the employee somehow delete those too?<p>Seems like at least two things went wrong.

Remember that scene in The Matrix where Cypher kills Switch and Apoc by unplugging them. "Not like this."<p>Wow. What a way to go.

and here is the link to the guys who fked them over:<p><a href="http://www.lagomorphics.com/" rel="nofollow">http://www.lagomorphics.com/</a><p>Its funny that they listed Journalspace under their "notable clients" section.

Interesting problem: how can you get to having backups if the person whose responsibility it would have been to take care of backups is the one who screws you over.<p>I guess this calls for technical CEOs...

having no tape backup is a crime