Openness by default might also discourage some of the possible negative uses of the XO, such as the problem that was recently reported in the media with pornography being discovered on Nigerian children's XOs. It could also (rather counter-intuitively) protect children from bullying and exploitation, if those around them, including their teacher, were more aware of what was going on in their life. Openness cures all sorts of societal ills.
<br><br><br><div><span class="gmail_quote">
On 8/24/07, <b class="gmail_sendername">Samuel Klein</b> <<a href="mailto:meta.sj@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">meta.sj@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is a private diary one of the core use cases we want to support?<br>That's not particularly collaborative, educational, or hard to achieve<br>without an XO.<br><br>Requiring extra effort to share things created on an XO network
<br>propagates unnecessary barriers that exist in closed online<br>communities today, and limits the impact of connection with those<br>around you.<br><br>Sharing is the natural state of a close-knit community -- in this
<br>
case, XO networks exist explicitly to make things that are shared, and<br>to track contribution and participation rather than ownership (a<br>notion which gets fuzzy as soon as collaboration begins). If you want<br>to do something different and private,, it should involve a conscious
<br>step.<br><br>SJ<br><br>On 8/24/07, Ivan Krstiæ <<a href="mailto:krstic@solarsail.hcs.harvard.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">krstic@solarsail.hcs.harvard.edu</a>> wrote:
<br>> On Aug 24, 2007, at 3:12 AM, Samuel Klein wrote:<br>> > Having user documents that are innately private runs counter to the
<br>> > principles of an environment designed for sharing. This is a familiar<br>> > model of ownership and privacy, but not necessarily an appropriate one<br>> > in this case.<br>><br>> You'll have a shot at convincing me after you've convinced Walter.
<br>> Personally, I really don't want kids to learn about privacy by virtue<br>> of having their diary splattered all over the mesh and web because<br>> things are public by default. I would refuse to use such a computer,
<br>> so I am loathe to give it to others. I am, however, entirely fine<br>> with a setting somewhere that lets interested kids _change_ the<br>> default to shared/public for documents.<br>><br>> --<br>> Ivan Krstiæ <
<a href="mailto:krstic@solarsail.hcs.harvard.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">krstic@solarsail.hcs.harvard.edu</a>> | <a href="http://radian.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://radian.org</a><br>_______________________________________________<br>Sugar mailing list<br><a href="mailto:Sugar@lists.laptop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Sugar@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/sugar" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.laptop.org/listinfo/sugar</a><br></blockquote></div><br>