Hi Damian,
On 5/23/12 7:27 PM, Damian Johnson wrote:
>> The bridge descriptor tarballs contain bridge network statuses, server
>> descriptors, and extra-info descriptors. See:
>>
>> https://metrics.torproject.org/data.html#bridgedesc
>
> Oops, I read 'contain similar documents as the relay descr
Thanks, Karsten!
> The bridge descriptor tarballs contain bridge network statuses, server
> descriptors, and extra-info descriptors. See:
>
> https://metrics.torproject.org/data.html#bridgedesc
Oops, I read 'contain similar documents as the relay descriptor
archives' as being server descriptors.
On 5/21/12 7:19 PM, Karsten Loesing wrote:
> On 5/21/12 5:55 PM, Damian Johnson wrote:
>> I didn't realize that bridge extrainfo descriptors _were_ sanitized.
>> What section of the format page details the scrubbing for those?
>
> Aha, good catch, that's not mentioned on the format page. Right no
Hi Damian,
On 5/21/12 5:55 PM, Damian Johnson wrote:
> Hi Karsten.
>
>> - Bridge network statuses contain a "published" line
>
> Oh, I didn't realize that there was a consensus that included bridges.
> Mind explaining where they come from and what they're for?
The bridge authority generates a b
Hi Karsten.
> - Bridge network statuses contain a "published" line
Oh, I didn't realize that there was a consensus that included bridges.
Mind explaining where they come from and what they're for? Which
category can I find these in on the metrics data page?
I haven't implemented network status e
Hi Damian,
I plan to make a few changes to the bridge descriptor sanitizer to
implement changes discussed on this list and in various Trac tickets.
The result will be format version 1.0. Here's what will change compared
to the current (unversioned) format. Can you take a look whether stem
would
