<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
* +1 to Sascha's very astute comments below.<br>Caryl<br><br>> From: sascha-ml-ui-sugar-soas@silbe.org<br>> To: soas@lists.sugarlabs.org<br>> Date: Sat, 19 Jun 2010 09:53:22 +0000<br>> Subject: Re: [SoaS] Limited Internet Access for SOAS<br>> <br>> Excerpts from Raffael Reichelt's message of Sat Jun 19 06:47:02 +0000 2010:<br>> <br>> > I had a talk with sebastian at linuxtag about including local squid<br>> > with a whitelist in soas.<br>> Censoring internet access with Sugar (or SoaS in this case) comes up<br>> regularly. If you really must filter (*), it's a task for the device<br>> providing internet access, not the client device (the computer running<br>> Sugar). One of the reasons is that it's way too easy ("kinderleicht"<br>> in german) to circumvent local filtering if the user has full access (as<br>> Sugar users do by design).<br>> <br>> <br>> (*) Whether filtering is a good idea / achieves what it's supposed to is<br>> a separate topic and doesn't belong on the SoaS list. Let me just<br>> mention that filters are very "dumb" tools with a lot of false<br>> positives AND negatives (e.g. some german blacklist even blocked<br>> Wikipedia). Having a filter can make the parents believe their kids<br>> are "safe" and stop supervising them. It's quite similar to anti-<br>> virus software and personal firewalls: they make you believe you are<br>> safe, while in fact you are not.<br>> <br>> Sascha<br>> <br>> -- <br>> http://sascha.silbe.org/<br>> http://www.infra-silbe.de/<br>                                            </body>
</html>