On Thu, Apr 16, 2015 at 06:48:53PM +, Yawning Angel wrote:
> On Thu, 16 Apr 2015 14:03:58 -0400 (EDT)
> "Steve Snyder" wrote:
> > The v0.5 binary is substantially larger than the v0.4 binary (7204KB
> > vs.5408KB, both built with Go v1.4.2).
> >
> > Is this expected behavior with the newer ve
On Thu, 16 Apr 2015 14:03:58 -0400 (EDT)
"Steve Snyder" wrote:
> The v0.5 binary is substantially larger than the v0.4 binary (7204KB
> vs.5408KB, both built with Go v1.4.2).
>
> Is this expected behavior with the newer version of obfs4proxy?
Building on linux/amd64 with 1.4.2 I get:
* 0.0.4 7
The v0.5 binary is substantially larger than the v0.4 binary (7204KB vs.5408KB,
both built with Go v1.4.2).
Is this expected behavior with the newer version of obfs4proxy?
On Wednesday, April 15, 2015 5:19pm, "Yawning Angel"
said:
> ___
> tor-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/04/15 21:18, nusenu wrote:
> Hi,
>
> I'm planing to store relay data in a database for analysis. I
> assume others have done so as well, so before going ahead and
> designing a db schema I'd like to make sure I didn't miss
> pre-existing db sch
On April 15, 2015 at 6:01:15 PM, Philipp Winter
(p...@nymity.ch(mailto:p...@nymity.ch)) wrote:
> On Tue, Apr 14, 2015 at 11:56:12AM +0200, Miquel Llobet wrote:
> > As far as coding goes, I played a bit with OONI (did a scan, turns out I'm
> > clean :-) ). and built it from source. What bugs
