The day of good and bad with WebSENSE.
Feb. 10th, 2006 04:48 pmBad: whoever's doing the filtering has caught on to archive.org. Ouch. The whole site isn't blocked, but you are blocked if you try to retrieve a URL that's already blocked.
Good: WebSENSE - or at least our install - doesn't block by IP on most sites. I found this out this afternoon by accident.
The kinda bad: I still have to find the IP address of the site and pray that they use relative URLs. It's more worthwhile to use my Sidekick to access non-work things during my breaks. Plus, the people who would find some use for this (my colleagues who don't have web-surfing cell phones) have no idea what I'm talking about.
I hate doing this, because I tend to preach about working with the system instead of going against it, but if there's a choice between doing my job and not being able to do it, I'm gonna bend the rules and do it. Sorry. Until the Great Bureaucracy gets its act together and frees us from WebSENSE, I'm going to do what I need to do.
I've exchanged a few emails with Mr. Lee, a supervisor (or the supervisor) of WebSENSE Database operations over issues related to WebSENSE and censorship, but I guess that a) he didn't feel that an employee of one of his clients was worth his time, b) he didn't like my stance on WebSENSE's categorization assisting with censorship, or c) He didn't like it pointed out that WebSENSE filters for the entire country of Yemen. Shame. I'm a proponent for freedom of access, and if you work for a censorware company, you're not gonna like what I've got to say. Period.
Good: WebSENSE - or at least our install - doesn't block by IP on most sites. I found this out this afternoon by accident.
The kinda bad: I still have to find the IP address of the site and pray that they use relative URLs. It's more worthwhile to use my Sidekick to access non-work things during my breaks. Plus, the people who would find some use for this (my colleagues who don't have web-surfing cell phones) have no idea what I'm talking about.
I hate doing this, because I tend to preach about working with the system instead of going against it, but if there's a choice between doing my job and not being able to do it, I'm gonna bend the rules and do it. Sorry. Until the Great Bureaucracy gets its act together and frees us from WebSENSE, I'm going to do what I need to do.
I've exchanged a few emails with Mr. Lee, a supervisor (or the supervisor) of WebSENSE Database operations over issues related to WebSENSE and censorship, but I guess that a) he didn't feel that an employee of one of his clients was worth his time, b) he didn't like my stance on WebSENSE's categorization assisting with censorship, or c) He didn't like it pointed out that WebSENSE filters for the entire country of Yemen. Shame. I'm a proponent for freedom of access, and if you work for a censorware company, you're not gonna like what I've got to say. Period.