Delivery-Date: Mon, 17 Nov 2014 18:02:45 -0500
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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id B32DE1E0C80;
	Mon, 17 Nov 2014 18:02:43 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C5C8131994;
	Mon, 17 Nov 2014 23:02:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5CEE8317B5
 for <tor-talk@lists.torproject.org>; Mon, 17 Nov 2014 23:02:36 +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 QXh7Tf7LTtAq for <tor-talk@lists.torproject.org>;
 Mon, 17 Nov 2014 23:02:36 +0000 (UTC)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com
 [IPv6:2607:f8b0:400c:c03::22f])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2D80A31786
 for <tor-talk@lists.torproject.org>; Mon, 17 Nov 2014 23:02:36 +0000 (UTC)
Received: by mail-vc0-f175.google.com with SMTP id hy10so3875890vcb.20
 for <tor-talk@lists.torproject.org>; Mon, 17 Nov 2014 15:02:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=JzdVEEuqa0TugfsxHereyIe3WJO3rM0AoMsxCfLTzpY=;
 b=SDBHL8x+t3fofRQ3HiyFhjZaBpbvPxyNSkTB19qCmTgxKgn/DG1R/CEMTHsl1cwQTI
 91zUCmO2zIoFPqgBNBYv8WqmJu1p25eu8p7Se6btV4jrgpRX998NaOspOQiiV96B3B/O
 n6xvvzAu6NUjG6/ZoaAli/79lCUQBllB2QtEeMGIWwWwewmOuOvT1PxQp9bRM9emlgnb
 ZPSEJ25RWXFkBb81JgBUFcEMRbh7v07dZFFQsrSINR8GY72C0y8ub89KHVSItYkxmupO
 /1GM0HXfFFcSk9Dp3w3MyZ97X9UEg+wgPz7pTF0x0bCs19PkA0zi5kPx9akqLL+wz2Nh
 tTHA==
MIME-Version: 1.0
X-Received: by 10.220.124.4 with SMTP id s4mr17651522vcr.38.1416265353882;
 Mon, 17 Nov 2014 15:02:33 -0800 (PST)
Received: by 10.221.64.74 with HTTP; Mon, 17 Nov 2014 15:02:33 -0800 (PST)
In-Reply-To: <CAFggDF0q10_0hVGVY-2d3Kpz5q1tJWPbeQbu=U86oYLE_yNwZg@mail.gmail.com>
References: <20140909000553.GN8132@moria.seul.org>
 <540F0F38.1090106@torproject.is>
 <20140914051654.GF36318@moria.seul.org>
 <CAFggDF0q10_0hVGVY-2d3Kpz5q1tJWPbeQbu=U86oYLE_yNwZg@mail.gmail.com>
Date: Mon, 17 Nov 2014 18:02:33 -0500
Message-ID: <CAD2Ti28j-MYP2Z9zCjsQ24NzuY+5TDg1=AJZ=xt2nbzO31ASsA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] What should our 31c3 talk be?
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>

>>> > I wonder what would be the most useful topic for this year?

Usage stories are important and need to be given voice.
Tech talks can be had nearly anytime, anywhere.
Then you have the big question... how did LEA do it?
Certainly there's time before 31c3 to analyse/follow these
cases and do some fishing among journalistic sources.
Of course any active bombshell that would affect the above
voices that need tools like Tor the most should not be held
back just for sake of making show at a conference.
-- 
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

