isis transcribed 6.6K bytes:
>* The hashed fingerprint (as is the case for bridges in onionoo)
>* The hashed ip:port
Actually, my apologies, I was quite tired when I wrote this and totally
completely wrong.
A hashed ip:port would be a terrible idea because IPv4 space is only 2^32 and
port
Hi Ondrej,
[I felt it is better to discuss this via email if you feel otherwise
feel free to move the discussion back to trac.]
even though it was also me requesting the use of HTTPS for the repos [1]
- and I'm glad it has been (partially) accepted and implemented I do not
follow your comment tha
Hi all,
NRL is effectively partnered with the Tor Project Inc. for the
SponsorR efforts. Our (NRL's) tasking is largely overlapping and
somewhat complementary to that of TPI. As such I thought it would be
good to mention the basics of what we are working on to better inform
and coordinate the pla
In the past few months of bridge user graphs, there is an apparent
negative correlation between obfs3 users and vanilla users: when one
goes up, the other goes down. If you draw a horizontal line at about
5500, they are almost mirror images of each other. I don't see it with
any other transport pai
George Kadianakis transcribed 4.1K bytes:
> Currently, OONI bridge reachability reports look like this:
> https://ooni.torproject.org/reports/0.1/CN/bridge_reachability-2014-07-02T21Z-AS4538-probe.yamloo
> and you can retrieve them from this directory listing:
> https://ooni.torproject.org/repo
On 20/10/14 14:37, George Kadianakis wrote:
> f) On a more researchy tone, this might also be a good point to start
>poking at the HS scalability project since it will really affect HS
>performance.
>
>We should look at Christopher Baines' ideas and write a Tor
>proposal out of the
