Matthew Finkel transcribed 1.6K bytes:
> On Sat, Oct 25, 2014 at 01:01:52PM +0200, Karsten Loesing wrote:
> > On 24/10/14 01:53, isis wrote:
> > > isis transcribed 6.6K bytes:
> > >>* The hashed fingerprint (as is the case for bridges in onionoo)
> > >>* The hashed ip:port
> > >
> > > Actu
On Sat, Oct 25, 2014 at 11:26:50AM +, Matthew Finkel wrote:
> On Sat, Oct 25, 2014 at 01:01:52PM +0200, Karsten Loesing wrote:
> > On 24/10/14 01:53, isis wrote:
> > > isis transcribed 6.6K bytes:
> > >>* The hashed fingerprint (as is the case for bridges in onionoo)
> > >>* The hashed
On Sat, Oct 25, 2014 at 01:01:52PM +0200, Karsten Loesing wrote:
> On 24/10/14 01:53, isis wrote:
> > 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 th
On 24/10/14 01:53, isis wrote:
> 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
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
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 10/7/14, 8:56 PM, Nima Fatemi wrote:
> This is awesome. one quick question tho. isn't it better to hash the
> fingerprints?
Yes you are right.
The fingerprints are now hashed.
~ Art.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists
Arturo Filastò wrote:
> On 10/7/14, 6:18 AM, M. C. McGrath wrote:
>>> The kind of data that they end up generating looks something like
>>> this:
>>> http://arturo.filasto.net/vizPlayground/bridge_rearchability.csv
>>
>> Nice- though the link seems to be dead for me (I get a 404). But it is
>> gr
On 10/7/14, 6:18 AM, M. C. McGrath wrote:
>> The kind of data that they end up generating looks something like
>> this:
>> http://arturo.filasto.net/vizPlayground/bridge_rearchability.csv
>
> Nice- though the link seems to be dead for me (I get a 404). But it is
> great that you are working on t
On 10/6/14, 6:28 PM, Matthew Finkel wrote:
> On Sat, Oct 04, 2014 at 06:27:22PM -0700, M. C. McGrath wrote:
>> These were a few possibilities for visualization that we came up with
>> at the OTF summit (I can send the full notes from that discussion if
>> everyone is okay with it):
Is this somethi
On Sat, Oct 04, 2014 at 06:27:22PM -0700, M. C. McGrath wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
> These were a few possibilities for visualization that we came up with
> at the OTF summit (I can send the full notes from that discussion if
> everyone is okay with it):
> -
== What is bridge reachability data? ==
By bridge reachability data I'm referring to information about which
Tor bridges are censored in different parts of the world.
The OONI project has been developing a test that allows probes in
censored countries to test which bridges are blocked and which a
12 matches
Mail list logo
