Here's an entertaining bit of email that has been forwarded around recently:
THE JOB - URINE TEST (Whoever wrote this one deserves a HUGE pat on the back!)
I HAVE TO PASS A URINE TEST FOR MY JOB... SO I AGREE 100%
Like a lot of folks in this state, I have a job. I work, they pay me. I pay my taxes and the government distributes my taxes as it sees fit. In order to get that paycheck, I am required to pass a random urine test with which I have no problem. What I do have a problem with is the distribution of my taxes to people who don't have to pass a urine test.
Shouldn't one have to pass a urine test to get a welfare check because I have to pass one to earn it for them? Please understand, I have no problem with helping people get back on their feet. I do, on the other hand, have a problem with helping someone sitting on their ASS, doing drugs, while I work. . . . Can you imagine how much money the state would save if people had to pass a urine test to get a public assistance check?
I guess we could title that program, 'Urine or You're Out'. Just a thought.
"The server which held the journalspace data had two large drives in a RAID configuration. As data is written (such as saving an item to the database), it's automatically copied to both drives, as a backup mechanism. The value of such a setup is that if one drive fails, the server keeps running, using the remaining drive. Since the remaining drive has a copy of the data on the other drive, the data is intact. The administrator simply replaces the drive that's gone bad, and the server is back to operating with two redundant drives. But that's not what happened here. There was no hardware failure. Both drives are operating fine; DriveSavers had no problem in making images of the drives. The data was simply gone. Overwritten. The data server had only one purpose: maintaining the journalspace database. There were no other web sites or processes running on the server, and it would be impossible for a software bug in journalspace to overwrite the drives, sector by sector. The list of potential causes for this disaster is a short one. It includes a catastrophic failure by the operating system (OS X Server, in case you're interested), or a deliberate effort. A disgruntled member of the Lagomorphics team sabotaged some key servers several months ago after he was caught stealing from the company; as awful as the thought is, we can't rule out the possibility of additional sabotage. But, clearly, we failed to take the steps to prevent this from happening. And for that we are very sorry. So, after nearly six years, journalspace is no more. If you haven't yet, visit Dorrie's Fun Forum; it's operated by a long-time journalspace member. If you're continuing your blog elsewhere, you can post the URL there so people can keep up with you. We're considering releasing the journalspace source code to the open source community. We may also sell the journalspace domain and trademarks. Follow us on twitter at twitter.com/jsupgrades for news."
What a shame. Over six years of data from multiple users. Gone.
If you happen to find errors or omissions in my work, I can assure you, they are NOT intentional. My nature is that of a worker- not a pedant. Every day I strive for three things- to SERVE, to DO and to IMPROVE. Please contact me with any comments, corrections or suggestions. Thank you. - J.N. Kish