I understood this problem to be solved already. We have the notion of sharing, and more specifically of scoping (with groups). If I write a story by myself, then it's private unless I explicitly say otherwise. If I draw a painting in an activity shared with the mesh, then I've already agreed that everyone should be able to see it. If I work on project with my study group, than likely that will have a "my study group" scope, and thus be available for anyone in my group to look at. We already have the notion of sharing and group scoping for privacy, so why wouldn't that determine the default scope of who can view what? This is a reasonable default that doesn't reduce privacy but is not strictly non-public.
- Eben On 8/24/07, Ivan Krstić <[EMAIL PROTECTED]> wrote: > > On Aug 24, 2007, at 3:12 AM, Samuel Klein wrote: > > Having user documents that are innately private runs counter to the > > principles of an environment designed for sharing. This is a familiar > > model of ownership and privacy, but not necessarily an appropriate one > > in this case. > > You'll have a shot at convincing me after you've convinced Walter. > Personally, I really don't want kids to learn about privacy by virtue > of having their diary splattered all over the mesh and web because > things are public by default. I would refuse to use such a computer, > so I am loathe to give it to others. I am, however, entirely fine > with a setting somewhere that lets interested kids _change_ the > default to shared/public for documents. > > -- > Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org > _______________________________________________ > Sugar mailing list > [email protected] > http://lists.laptop.org/listinfo/sugar >
_______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
