On 20/10/13 07:02, David Fifield wrote:
It's not that I'm trying to neglect unglamorous development--I'm really
not. This is how I see it: As a software engineer, I am always trying to
reduce risk. Refactoring code reduces risk in the long term but
increases risk in the short term. Sticking
On 19/10/13 06:31, David Fifield wrote:
On Mon, Oct 14, 2013 at 09:14:25PM +0100, Ximin Luo wrote:
Specific remaining tasks:
- merge #9349, #6810, #9974
- push #7167 to an official tpo repo
- do #9976, and #7167#comment:42 might require an obfsproxy fix
I agree with this, except that I
On 01/10/13 03:13, Tom Lowenthal wrote:
Combine obfuscation (obfsproxy) with address-diversity (flashproxy) [#11]
---
**[On Track: Minimal]** The work of integrating obfsproxy with
flashproxy is done. George will include this in
Matt Pagan:
There still exists a bug in Mumble such that when network connections
are routed through a proxy they leak DNS requests. This past month I've
been reading QT documentation so that I can understand the Mumble code
better and find the bug. After the meeting on IRC, velope suggested
Today, at 1100 Pacific, we spent more than 90 minutes discussing
[Sponsor F][]. Here's the summary.
**READ THIS**: The next Sponsor F meeting will be held in a mere two
weeks on **2013-10-14, at 1100h Pacific in #tor-dev**.
This is a schedule change: from now on, the meetings will be every two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/09/13 09:13 PM, Tom Lowenthal wrote:
Today, at 1100 Pacific, we spent more than 90 minutes discussing
[Sponsor F][]. Here's the summary.
**READ THIS**: The next Sponsor F meeting will be held in a mere
two weeks on **2013-10-14, at
On Mon, 30 Sep 2013 19:13:37 -0700
Tom Lowenthal m...@tomlowenthal.com wrote:
Today, at 1100 Pacific, we spent more than 90 minutes discussing
[Sponsor F][]. Here's the summary.
**READ THIS**: The next Sponsor F meeting will be held in a mere two
weeks on **2013-10-14, at 1100h Pacific in
