This is a bit outside of my area but shouldn't VS2013 Express support C99? That
is available for free.
Yaron
From: tor-dev on behalf of
?
Sent: Thursday, October 16, 2014 11:33 AM
To: tor-dev@lists.torproject.org
Subject: Re: [tor-dev] Bu
On Thu, Oct 16, 2014 at 02:16:32PM -0400, Nick Mathewson wrote:
> On Thu, Oct 16, 2014 at 7:40 AM, Владимир Мартьянов
> wrote:
> > Hi all! I'm new at this list :-)
> >
> > I decided to understand how TOR works and I want to build it in VS to debug
> > it and explore it's internals. I have Visual S
18:21 < nickm> tjr: are you still around?
18:26 < tjr> nickm: Yup
18:27 < nickm> So, speaking generally as a reaction: Yeah!
Bootstrapping Tor from zero should work better and be easier. If you
want to push us that way, we'll get there. If not, there are other
ways you can help us get there.
18:2
As far as I know only Visual Studio 2013 has C99 support. Upgrade to VS2013
costs about 300$ for commercial versions, a lot of code was written in
earlier versions...
By the way, I fixed only about 10 lines of code and finally I managed to
build the TOR using VS2008, so i think it's not so hard to
On Thu, Oct 16, 2014 at 7:40 AM, Владимир Мартьянов
wrote:
> Hi all! I'm new at this list :-)
>
> I decided to understand how TOR works and I want to build it in VS to debug
> it and explore it's internals. I have Visual Studio on my first PC and I got
> errors during build on address.c. I investi
Hi all
For the last couple of days i've been thinking about the visualization
of the bridge reachability data and how it relates to the currently
deployed ooni [7] system, here are the conclussions:
== Variables ==
I think that the statistical variables for the bridge reachability
reports are:
- S
Hi all! I'm new at this list :-)
I decided to understand how TOR works and I want to build it in VS to debug
it and explore it's internals. I have Visual Studio on my first PC and I
got errors during build on address.c. I investigated the reason: commit
0ca83872468af59b94e14fe7fdfcb38cb5a3f496
I
Karsten Loesing transcribed 4.5K bytes:
> On 16/10/14 10:57, isis wrote:
>
> Having private bridges in public bundles is actually harmful, because it
> makes it look like bridges are not much used. If we want to suggest
> bridge development or BridgeDB development to a sponsor and they look at
>
On 16/10/14 10:57, isis wrote:
> Karsten Loesing transcribed 1.9K bytes:
>> On 16/10/14 09:06, isis wrote:
>>> Roger Dingledine transcribed 1.0K bytes:
Your best bet at a short-term hack might be to add a line to the
descriptor which politely asks bridgedb not to give its address out
Karsten Loesing transcribed 1.9K bytes:
> On 16/10/14 09:06, isis wrote:
> > Roger Dingledine transcribed 1.0K bytes:
> >>
> >> Your best bet at a short-term hack might be to add a line to the
> >> descriptor which politely asks bridgedb not to give its address out.
> >
> > Interesting idea...
> >
On 16/10/14 09:06, isis wrote:
> Roger Dingledine transcribed 1.0K bytes:
>> On Mon, Oct 13, 2014 at 09:44:24PM -0700, David Fifield wrote:
>>> Is there a way to send
>>> metrics data without also ending up in BridgeDB?
>>
>> Alas, not currently. That's because the metrics data is a side effect
>>
Roger Dingledine transcribed 1.0K bytes:
> On Mon, Oct 13, 2014 at 09:44:24PM -0700, David Fifield wrote:
> > Is there a way to send
> > metrics data without also ending up in BridgeDB?
>
> Alas, not currently. That's because the metrics data is a side effect
> of the bridge authority / bridgedb d
12 matches
Mail list logo
