ScienceOnline09: Hey, You Can’t Say That!
![]() ideonexus Blocked at the Coast Guard Base |
In the interest of enabling attendees to speak candidly about personal conflicts they have experience between their professional or personal lives and their online persona, speakers were kept anonymous for this session (not sure how posting their names on the conference program affects this). It was suggested that all panelists should be referred to as {PZ1, PZ2, PZ3…} in honor of Science Blogs’ most controversial author, PZ Myers of Pharyngula fame, who couldn’t make it.
This session was also the most packed of all, and had some of the most interesting stories. PZ2 talked about how his employer wanted to put an editor on his blog, and how he expects to be fired any moment now for refusing to allow it. PZ3 talked about her employer took no interest in her personal blog until they thought they could benefit from its publicity. Another blogger talked about how he had to stop criticizing a company on his blog when he started receiving grant money from them.
One attendee talked about how someone dredged up an inflammatory post he had written years ago and submitted it to his present employer, demanding action. The employer, luckily, was sophisticated enough to realize the post was a personal one and did not represent the publication, but it does raise the idea of our online histories coming back to haunt us, not all of it under our control. Someone suggested that people should blog respectfully under their real name as a means of pushing the unfavorable websites down the search results.
I thought PZ3 had one of the most insightful observations, when she talked about the naivety of scientists, and their belief in intellectual honesty. It doesn’t occur to them that they can’t speak their mind.
“We need a bloggers union,” someone said, and someone else mentioned the Online News Association.
At the very end of the session, a moderator asked if there were any bloggers who worked for the Federal Government who had some stories to share. I didn’t think there was enough time left to squeeze in my experiences, but because I work for the Federal Government, on a Coast Guard base, I have to be extremely careful about my online actions while on my work computer.
Five years ago, I quite foolishly downloaded my ideonexus beta blog to my server at work to make some tweaks on my lunch break. It just happened that we were undergoing a security audit that week, and guess what they found when they looked at my computer?
I got pulled into the Project Manager’s office, where my blog, specifically a political rant, was pulled up in a browser window, being broadcast from my workstation to the intranet. After being properly chewed out, I was made to sign a statement that I would be fired if I ever screwed up like this again.
The real issue, I would learn later, wasn’t that I was using my workstation for non-work activities during my break, it was that I was using my computer to post political content that others could read. It is seriously illegal to use Federal property to promote a political ideology, and it would have been proper to fire me on the spot.
Recently, CGblog has me identified as an unofficial Coast Guard blogger; although, my blog really has very little to do with the Coast Guard, except for my post on Phytoremediation projects on base. This isn’t a big deal, as everyone at work knows I blog science and geekery for the local paper, but I do have two posts out there that could catch me some heat. One post brags about my ridiculously expensive tax-payer-funded chair and another jokes about getting away with having the Flying Spaghetti Monster on my desk.
Is there a Sword of Damocles hanging over my head?












Are they blocking your site just to ensure you don’t use federal property to blog? That would almost make sense.
Either way, it’s good that you’re not going to back down about blogging! Obviously!
Comment by ClintJCL — January 23, 2009 @ 5:53 pm
You would not believe what one finds on some federal or gov sites (in any country) from porn to ordering illegal weapons. Even if it is with your own money, it does not look good for the firm. So as much as I love your blog, which I read with religious fervor, I still think that it has no place on your workplace. It seems good sense to me to avoid to be traced to an address (the workplace address, host name, IP, etc) that belongs not to you but to your employer’s, for your own stuff that he knows nothing about (good, bad or neutral). It is not censorship: it is about you protecting your employer’s interests – and if you do not want to care for it, maybe it is time to quit.
Comment by claude lambert — January 24, 2009 @ 11:23 am
It’s absolutely not censorship, I totally agree with both of you on that, and I didn’t mean to make it sound like I was saying what I did was okay. That was just a bone-headed thing I did more than five years ago.
As far as blogging from work. I don’t do that. The block on my website goes for all blogs because people getting addicted to comment threads is a problem. At our federal institution, we are allowed two 15 minute web-surfing breaks a day. Blogs, porn, and streaming video sites are blocked for content and bandwidth reasons, which makes sense.
I actually appreciate not being able to access my blog from work to avoid the temptation. The web-filter provides a nice distinction between my work and home life; although, it does mean I can’t find the time to respond to comments and e-mails but once a week.
As far as my concerns go, the Coast Guard seems to respect that my online life at home is separate and distinct from my work life. I do worry about coworkers reading my blog, but the good side of that is that it keeps me honest (which is also why I blog under my full name). : )
Comment by ideonexus — January 24, 2009 @ 12:46 pm
I still think it’s censorship. :)
Comment by ClintJCL — January 24, 2009 @ 2:02 pm
[...] know from previous experience that I need to be careful about what I put in the root directory on my development box at work, but [...]
Pingback by This is What Happens When You Leave a Port Open on a DHS System | ideonexus.com — February 26, 2009 @ 2:01 pm