Hi,
On 06/01/18 15:52, Iain Learmonth wrote:
> Ok, I'll see if I can do a quick hack workaround to generate the list
> for Relay Search until the data is available through Tor Metrics.
In fact, my original quick hack workaround still works, as it's only
extracting fingerprints. (Tested that
Hi,
On 05/01/18 22:33, teor wrote:
> The fallback 2.0.0 spec hasn't been merged yet, but atagar has reviewed it.
> It's at:
> https://github.com/teor2345/torspec/blob/fallback-format-2-v2/fallback-spec.txt
I've added this link to the Metrics ticket #24434, I started work on
this but ran out of
Hi,
> On 27 Dec 2017, at 21:53, teor wrote:
>
>>> On 26 Dec 2017, at 18:47, teor wrote:
>>>
>>> On 25 Dec 2017, at 07:26, Iain Learmonth wrote:
>>>
>>> As we are planning to also add a parser to metrics-lib (#24434), would
>>> it
> On 26 Dec 2017, at 18:47, teor wrote:
>
>> On 25 Dec 2017, at 07:26, Iain Learmonth wrote:
>>
>> As we are planning to also add a parser to metrics-lib (#24434), would
>> it be possible to get a full description of the format of the file
>> possibly
> On 25 Dec 2017, at 07:13, Damian Johnson wrote:
>
>> Done!
>>
>> * the file now starts with a type and a version line:
>> /* type=fallback */
>> /* version=2.0.0 */
>> * extrainfo is mandatory (occasionally we won't get a descriptor, so
>> we'll warn and mark the
Hi,
On 24/12/17 20:13, Damian Johnson wrote.
As we are planning to also add a parser to metrics-lib (#24434), would
it be possible to get a full description of the format of the file
possibly in RFC5234 format so that we can check that the generator and
parsers all match up to that
> Done!
>
> * the file now starts with a type and a version line:
> /* type=fallback */
> /* version=2.0.0 */
> * extrainfo is mandatory (occasionally we won't get a descriptor, so
> we'll warn and mark the relay extrainfo=0)
> * each fallback entry ends with /* = */
Sweet, thanks Tim!
> On 24 Dec 2017, at 11:14, Damian Johnson wrote:
>
>> Do you want me to add an explicit end of record comment, or is the
>> comma sufficient?
>
> Hi Tim. I'd rather not rely on just a comma. I can easily see us
> tweaking the layout so 'expect a line with only a comma'
> Do you want me to add an explicit end of record comment, or is the
> comma sufficient?
Hi Tim. I'd rather not rely on just a comma. I can easily see us
tweaking the layout so 'expect a line with only a comma' breaks.
I actually like both of the other suggested options: having
'extrainfo=0' so
> On 24 Dec 2017, at 08:16, Damian Johnson wrote:
>
> Hi Tim, added preliminary Stem parsing support for the v2 fallback format...
>
> https://gitweb.torproject.org/stem.git/commit/?id=ea55eaa
>
> Few thoughts are...
>
> * It would be nice if the 'extrainfo=' lines
Hi Tim, added preliminary Stem parsing support for the v2 fallback format...
https://gitweb.torproject.org/stem.git/commit/?id=ea55eaa
Few thoughts are...
* It would be nice if the 'extrainfo=' lines were mandatory since I
need a delimiter between the entries.
* Maybe we should start the
Hi
I just added the DownloadExtraInfo in the config file for the nodes
"chulak" and "aurora".
Greetings
teor:
> Hi all,
>
> Some time in the next few weeks, the Tor fallback directory mirror file
> format will change. This affects stem and Relay Search, which parse this
> file.
>
>
>
Hi all,
Some time in the next few weeks, the Tor fallback directory mirror file
format will change. This affects stem and Relay Search, which parse this
file.
Change Description
Here is a list of changes to the file format:
* the "weight" line has been removed, and replaced with a Tor config
13 matches
Mail list logo