 |
 |
 |
 |
 |
|
||||||||
|
||||||||
|
Two summers ago, when I did a workshop in a district that was just getting up and running with computers, the conversation got around to filtering. I asked if they had filtering in place in the district. They said yes. So I told them I would show them how the filter reacted to an inappropriate site. I then asked to an inappropriate search term. I don't remember what was said. For the sake of this example we will say that they said "boobs". I didn't do a search. I just went to the browser and typed in http//www.boobs.com and hit enter. To my surprise, it was not blocked and I had hit a site that takes control of the browser. Every time I closed a window, another opened up. After about a minute of this, half of the teachers were in shock and the other half were laughing and half wondering whether it was a set up. Just about this time the principal, superintendent, and technology coordinator came in the room. Fortunately, I knew them and explained I was showing the teachers how well the district filter worked. At that point, the tech coordinator informed me that it was summer, there were no student in the building, they worked on the firewall the day before and the filter was not turned on. To everyone's relief, that seemed to explain the situation, but needless to say, the discussion went on for a while and the teachers realized the role they had to play in working with kids to teach them how to handle a variety of situations. But that's not the strange part. Here's the part I couldn't have scripted. For some unknown reason, before sending off the message on 4/11/01, I went to my FILTERED station and typed in http//www.boobs.com and guess what? That's right. IT WASN'T BLOCKED. [ BACK ] |
|
© 2006 Online Internet Institute. |