Delivery-Date: Sun, 05 Jun 2016 17:21:30 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [138.201.14.202])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id CEC931E0056;
	Sun,  5 Jun 2016 17:21:28 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 84200E09CA;
	Sun,  5 Jun 2016 21:21:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C5230E09CA
 for <tor-talk@lists.torproject.org>; Sun,  5 Jun 2016 21:20:55 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0Dvb590eyjVL for <tor-talk@lists.torproject.org>;
 Sun,  5 Jun 2016 21:20:55 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 89EA6E09C7
 for <tor-talk@lists.torproject.org>; Sun,  5 Jun 2016 21:20:55 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 3C0461A587B
 for <tor-talk@lists.torproject.org>; Sun,  5 Jun 2016 21:20:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1465161651; bh=wPvNVc+qM7noD6B/yLYP6IA6s+4RkKDvQ0KH7Y8cOSE=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=W3ULOiGUjH3dlvekysPtij95U4E5CyyNicvFu3NUe5lhRDQ+Ntse/CFnUx85yBef0
 MaM5qo0hlKbVUvZgkQNUQMfTwknjhs+JQFbjwu772phwyOmAWqKEHSNfQJBmeeZ4f7
 X5BKKnhVrehAWptQaLFHx2gUyDga7WVlkDKJ0+s0=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 966A71C0322
To: tor-talk@lists.torproject.org
References: <1050651465068654@web3m.yandex.ru>
 <CAGRDzQVfJxyJUZTUM8ygH8qsv-v7KLCFr8M1DuPtBp81fQO4=Q@mail.gmail.com>
 <CAG2tMp7heUnE8BhByGfmWToyR4CmPWPz09e6QSQrR0yFtUvGCQ@mail.gmail.com>
 <CAGRDzQVeo82mwcYLPTZMo_vSZYfeSEMQyS+dn9JqsRUAQTtoyQ@mail.gmail.com>
 <5753795B.5010906@riseup.net>
 <CAGRDzQWTYfqZbS2qteVGW4pGZsXG6VX03JexeXSfbFba4G-WRw@mail.gmail.com>
 <CAGRDzQUPF6aYj1ZyOnq7a4d4Tfdpy=UHAnvNf6kyNubHW3vTmQ@mail.gmail.com>
 <CAGRDzQU1M10ASY1PP8BRmH8Cz=gg5fSOFpRPb_a5uSx5NZy1EA@mail.gmail.com>
 <CAGRDzQVVSHBR3zGkuC6aQUKPksiUWryK5r+0JRd30Gbe_WGqiQ@mail.gmail.com>
 <5753A212.1010401@riseup.net>
 <CAGRDzQVONF77ULHucu0sAOBqNQjhtCGwrrA8vLjyoFv+YPDqaA@mail.gmail.com>
From: Mirimir <mirimir@riseup.net>
Message-ID: <575497B0.8050603@riseup.net>
Date: Sun, 5 Jun 2016 15:20:48 -0600
MIME-Version: 1.0
In-Reply-To: <CAGRDzQVONF77ULHucu0sAOBqNQjhtCGwrrA8vLjyoFv+YPDqaA@mail.gmail.com>
Subject: Re: [tor-talk] Any updates from Tor Project on ioerror?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 06/05/2016 03:55 AM, Cari Machet wrote:
> it was umn ... sarcasm

Dude, you need to flag that in text comms :)

> that any organization has not inset into its guidelines ways of really
> structurally dealing with sexual misconduct is profoundly unethical
> 
> just another way tor is super fucked up
> 
> 
> On Sun, Jun 5, 2016 at 6:52 AM, Mirimir <mirimir@riseup.net> wrote:
> 
>> On 06/04/2016 09:38 PM, Cari Machet wrote:
>>> Why would any orginization ever set up best practices in order to really
>> be
>>> dealing with sexual misconduct of an employee ? Why consider such levels
>> of
>>> ethics ? Wierd.
>>
>> Because otherwise there will be expensive civil liability, no?
>>
>>> On Jun 5, 2016 3:59 AM, "Mirimir" <mirimir@riseup.net> wrote:
>>>
>>> I don't see that this link to a statement from Shari Steele has been
>>> posted yet: https://blog.torproject.org/blog/statement.
>>>
>>> She concludes: "We expect that this will be our only public statement."
>>>
>>> --
>>> tor-talk mailing list - tor-talk@lists.torproject.org
>>> To unsubscribe or change other settings go to
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>>>
>> --
>> tor-talk mailing list - tor-talk@lists.torproject.org
>> To unsubscribe or change other settings go to
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>>
> 
> 
> 
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

