There have been some comments about various aspects of Parental Controls being overwhelming, specifically in this post. It is true that some of the existing parental control companies will not be so keen on some features, however there is a lot of area for new features and things that are missing from Vista parental controls to be expanded into, like https filtering.
Looking at the overwhelming aspects, the main problem feature there is the application overrides. This is difficult to setup for parents unless you know something about how the programs are layed out on the computer. Sadly there is not really much we can do about this, it is a difficult problem to solve. I think this is one feature that most parents will not use, or will turn on and not know how to use it then turn it off again. Game settings I don't think are that overwhelming, the ability to change the rating system is there but it is not easy to get at and most parents will most likely not even know the option exists. The default setting will be set to the rating system for the area windows is sold in.
The logs are very useful, the problem there is how to present the information about things like web sites visited in a way that is easy to understand. For time constraint reasons we only did a very simple web log viewer in Vista, this is an area that third party tools could be useful. Writing an enhanced log viewer for the vista parental controls. All of the logs are in the Crimson logs as outlined in other sections of this log.
Overall I think that parents will use all of the features (including the activity reports) with the exception of application restrictions.
I happen to agree, the only section that may be overwhelming for the casual user is the Allow and Block Specific Programs section. For a hard core user it's great, but for a casual parent trying to lock down the computer, I can see the confusion it will
I just finished my tutorial on Setting up Parental controls where I went into detail about every single option. It was a long but interesting experience. The tute can be found here:
I noticed a few odd things when playing with the web allow block lists files. One is you do not allow : other than in http://. This makes it impossible to block URLs with non-standard ports like
http://www.example.com:81. Another issue is that you can't have an URL with a & in it. I see and understand why when you have a ? for a GET argument in an URL it is stripped so only the specific
page is added to the list, but why couldn't that have been done with the ampersands as well? With the way its currently setup it is very hard to do automatic conversion of known bad site lists to the new file format for Parental Controls.
Btw, glad I stumbled on to this site. Very limited resources on parental controls currently.
Interesting points, I don't think we allow you to block www.frog.com:81 any differently than www.frog.com. So if you block one, the other is blocked too.
Can you show me some examples of bad site lists? Sounds like something that would be interesting to do, having a program that would convert the known block lists into the parental controls system.
Ahh..that is good to hear about the non-standard ports. Just tested it and your right it does block it as well.
Some examples of bad site lists are:
There are a few others but those are what I feel the best of breed. I have already contacted the creator the MVP Hosts file