Difference between revisions of "Features/Parental controls"
< Features
Jump to navigation
Jump to search
Tonyforster (talk | contribs) |
Tonyforster (talk | contribs) |
||
| Line 14: | Line 14: | ||
==Effectiveness== | ==Effectiveness== | ||
| + | There are a number of potential ways to circumvent parental controls | ||
| + | |||
| + | * switching to Gnome | ||
| + | * using Pippy to create a browser | ||
| + | * using Turtle Blocks to create a browser (yes its easy!) | ||
| + | * using Develop to create a browser | ||
| + | * cloning an Activity | ||
| + | * installing another browser Activity | ||
| + | * installing Browse with an altered name | ||
| + | * reflashing with a different build | ||
==Unintended consequences== | ==Unintended consequences== | ||
Revision as of 21:05, 23 April 2014
The proposal
Default or optional feature
Marketing case
"Not only am I basing this on the inclusion of a similar feature in OS X, I am also basing this on the fact that some Nigerian children reportedly visited a Web site containing pornography. I have no other evidence." (Ryan)
How often would this feature be used? How do we estimate this?
Education case
Does this feature enhance or detract from Sugar's effectiveness for facilitating learning.
A central platform of OLPC and Sugar is that children should be creators rather than consumers. This has been facilitated in a number of ways, show source, cloning Activities, easy reflashing of the OS. Any locking down of the software would be inconsistent with the design philosophy.
Effectiveness
There are a number of potential ways to circumvent parental controls
- switching to Gnome
- using Pippy to create a browser
- using Turtle Blocks to create a browser (yes its easy!)
- using Develop to create a browser
- cloning an Activity
- installing another browser Activity
- installing Browse with an altered name
- reflashing with a different build