Delivery-Date: Sun, 05 Jun 2016 19:42:23 -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 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 D8D361E0080;
	Sun,  5 Jun 2016 19:42:20 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1D659E0E61;
	Sun,  5 Jun 2016 23:42:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8D34FE0B56
 for <tor-talk@lists.torproject.org>; Sun,  5 Jun 2016 23:42:12 +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 kWD1QZZtColV for <tor-talk@lists.torproject.org>;
 Sun,  5 Jun 2016 23:42:12 +0000 (UTC)
Received: from forward11h.cmail.yandex.net (forward11h.cmail.yandex.net
 [87.250.230.153])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 58BA1E09A8
 for <tor-talk@lists.torproject.org>; Sun,  5 Jun 2016 23:42:12 +0000 (UTC)
Received: from smtp2h.mail.yandex.net (smtp2h.mail.yandex.net
 [IPv6:2a02:6b8:0:f05::116])
 by forward11h.cmail.yandex.net (Yandex) with ESMTP id 6D3C82134B
 for <tor-talk@lists.torproject.org>; Mon,  6 Jun 2016 02:41:37 +0300 (MSK)
Received: from smtp2h.mail.yandex.net (localhost [127.0.0.1])
 by smtp2h.mail.yandex.net (Yandex) with ESMTP id 28B4C1700352
 for <tor-talk@lists.torproject.org>; Mon,  6 Jun 2016 02:41:36 +0300 (MSK)
Received: by smtp2h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id
 gZfWEeY7ss-fZ7m1BsJ; Mon, 06 Jun 2016 02:41:36 +0300
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client certificate not present)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cajuntechie.org; s=mail;
 t=1465170096; bh=K9/aZHda4OKOOLOGGsNnp39jl5xppECLckV59L/tSHA=;
 h=Subject:To:References:From:Openpgp:Message-ID:Date:User-Agent:
 MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding;
 b=V6y4NXdwxY2DIm5P4GjcoE+2bbdd7pW7G5xmidy5sNIKld3QGHhHsirs2G75c5jdk
 Q2EWpoLwZpSZDjge8HwLURODSpprTeapE6/soFuqvnVi43ReQEmBzA8Wwua0vCOTmC
 GQZSqeONxgft2tVkN13d9qbB4L6saaFTapB0IcHY=
Authentication-Results: smtp2h.mail.yandex.net;
 dkim=pass header.i=@cajuntechie.org
X-Yandex-ForeignMX: DE
X-Yandex-Suid-Status: 1 0
To: tor-talk@lists.torproject.org
References: <51c9eb8d-bcfc-cce0-02b8-18c4c544a7de@cajuntechie.org>
 <dc9f4b61575bb70ece1a2b94449910c8@riseup.net>
 <1ae5122a-7654-28e2-1481-65648a7816de@cajuntechie.org>
 <5754B61F.6070204@riseup.net> <77a33e5205fc5e32d325bc6ba4c7f1b4@riseup.net>
From: Anthony Papillion <anthony@cajuntechie.org>
Openpgp: id=C5CEE687DDC2D12B906356EA028ADF7453B04B15
Message-ID: <c512ba8d-21f5-e1ce-4611-a999824abaf6@cajuntechie.org>
Date: Sun, 5 Jun 2016 18:41:37 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <77a33e5205fc5e32d325bc6ba4c7f1b4@riseup.net>
Subject: Re: [tor-talk] [OFF-LIST] Re: Has anyone HEARD from IOError since
 his last tweet?
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 6/5/2016 6:35 PM, notfriendly@riseup.net wrote:
> On 2016-06-05 19:30, Mirimir wrote:
>> On 06/05/2016 05:14 PM, Anthony Papillion wrote:
>>> On 6/5/2016 5:43 PM, notfriendly@riseup.net wrote:
>>>> On 2016-06-05 18:17, Anthony Papillion wrote: The last time
>>>> IOError tweeted was on 30 May. Has anyone on this list
>>>> actually HEARD from him since then? We have to remember that
>>>> Jake comes from a really fucked up childhood. Something like
>>>> these allegations could push someone over the edge.
>>> 
>>>> Anthony
>>> 
>>> 
>>>> He might need time to himself for now. He has a lot of
>>>> people talking about him right now. He probably needs a
>>>> break.
>>> 
>>> You're probably right. I've just seen this kind of thing get
>>> out of hand before and, innocent or not, people can be pushed
>>> over the edge.
>> 
>> I get where you're coming from, but public comments about his
>> history, and speculation about suicide, really aren't
>> appropriate. IMHO, anyway.
>> 
>> Just sayin'.
> I agree with that. We shouldn't assume someone died just because
> they are not responding to online communications. The speculation
> is suicide as you said is indefinably inappropriate. He might need
> a break. Another possibility is that he is in an area with a power
> or internet outage (I'm not sure why long term but still). These
> are all possibilities.

I'm pretty sure I never said he had suicided so there's no
'assumption' there. What I did say is that, in light of the stress
he's under, someone should at least check on him. I mean yes there are
other possibilities but nothing should be flippantly ruled out. At
what point is it 'appropriate' to be concerned? A month? A year?
Never? If we never hear from him again should we simply assume he's
alright and just decided to check out of the community? I guess we're
all allowed our opinions but I choose to err on the side of concern
for a fellow human being who's directly impacted my life. Your choices
might be different.



-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXVLiwAAoJEAKK33RTsEsV+gkP/RFuj5jFnglZ/FAAsmrZPjqR
oqDoWbr8axbhw1m7TkI1uGN+YGgLLuK+VsSCtPlQn+J9KN8pj38SvpVzIPA/1Dke
snPdyA59BkE95oN5dkRmzuDT0y9yujgKXOBn/h33pfyRV259lGseJLDzf6y5IcCq
7pSWeoDEBnWqt0LjdLODOQrRCti1Vdiu32tNf5vUQRgX4r1bNvMUPu/xTDcR6/K9
m2zf56ejIgDuiu6wXb1Hu+9Vi5p27UWibt4NvExpxBTCbF9ajbpI4EZtKQi81R1B
JzsNHQS5O2Mg9daCuOYgf0pLXbuhozDeXdoH4mmwTZvkOqoBv843hJl8SrXnZZPK
B6i7kQ0wx0dTMUpbacN3oNLYSaBDdXgDe3HqxRBqWXhTcCEMP0LMzQJ8TEljuYOv
6c3ZMnrOh6hMm1h5ScWSK/MGTil7392PPzt8/MdGWTjwGTq2X+KXhIjfsT6qQ9rz
fg/QgBBNaRFCYLKzEWV+k9JHU8SyFEoI5VK89W39K+sZeemFmTcyOwTFnGPyeBIi
mO7udvZiFyeBoc0r4mYAMh16mcP1JycaG5WSYvA5KlwuUqVWljpyXHp4ib3Og28B
z/cidAxOpaC9jBjZqvmqXbfi3dzzPWd7DWOKsI9k0BPMtWyUuReVutrDnbye/SOk
tGeDevtxHSsxgibhq7MI
=akKt
-----END PGP SIGNATURE-----
-- 
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

