It came to my attention recently that my blog has been designated “adult content” by the security software Websense. As a result, any network that uses Websense, including my employer’s network, will block access to my blog.
Adult content? Seriously? Websense defines adult content as:
Sites that display full or partial nudity in a sexual context, but not sexual activity; erotica; sexual paraphernalia; sex-oriented businesses as clubs, nightclubs, escort services; and sites supporting the online purchase of such goods and services.
I know there are loads of pics of beautiful women in bikinis posted here, but it’s not like there’s anything that could remotely qualify as pr0n. If my blog were a movie, it would easily get a PG-13 rating, no editing required. You won’t see anything here you wouldn’t see on a typical episode of Baywatch.
This development is definitely a serious inconvenience. When lunchtime rolls around, I like to check the blog for new comments. I also like to check out the blogs in my blogroll. Thanks to Websense, these activities are no longer an option. Also, anyone who checks my blog from their work won’t be able to if there network uses Websense.
Beyond the inconvenience, there’s another issue at play here. My name, my real name, is attached to this blog. If someone Googles my name from a Websense-using network, and they find this blog, they’re going to get the dreaded adult content blockage. In essence, Websense has branded me a pornographer. Not a good label to bear if you’re applying for a job.
So I’m going to have to find a solution to this situation. I’ve given serious consideration to switching to WordPress. But that still leaves the question of what to do about this blog and it’s unearned scarlet letter. I’m probably going to email Websense to see if they
can will help me. I’ll keep you posted.
Update: Comments have been closed for this post because dirtbag spammers have already started showing up here. That didn’t take long, did it?