[liberationtech] [Air-L] (advice sought) Public safety and configuration of list

[Yosem Companys]

Dear All,

Michael asked that the Program on Liberation Technology at Stanford
University overrule the list vote over safety issues because he said the
position created a potential legal liability for the university.

We informed Michael that we saw none and that the list subscribers had
taken the perceived safety issue into consideration when voting; in fact,
we included the links to the pros and cons that addressed the perceived
safety concerns.

Michael, however, insists that there are safety issues.  We remained
unconvinced.  He asked that we discuss the issue internally at Stanford
University.

Our final decision is consistent with the view that Jeremy outlined below,
which is common practice for mailing lists:  Email users are responsible
for their use of email, on a list or off, so they are responsible for
knowing the settings and adapting their behaviors to them.  The locus of
action of the list is the user, the administrator just sets the terms.

Moreover, we inform users of the risks associated with subscribing to
public lists both when they sign up and in our list guidelines.  We also
clearly state that the list is configured to reply to all.

As a result, the current option will remain as currently configured and
voted upon by list subscribers -- that is, reply to all.

As we have received numerous complaints over having administrative issues
crowd out substantive discussion on the list, we are creating a separate
"liberationtech-admin" list.  As soon as that list is operational, we will
let you know.  In the meantime, out of respect to your fellow subscribers,
we ask that you please refrain from further discussion about the issue here
but encourage you to continue the discussion there, if interested.

Best,

Yosem
One of your list moderators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/liberationtech/attachments/20130424/2fe308b2/attachment.html>