-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 22:37, nusenu wrote:
>> You mean instead of:
>
>> {"version":"2.3", "relays_published":"2015-04-25 18:00:00",
>> "relays":[
>> {"n":"shadowmourne","f":"1F515F1D420B498D9687658F4A3D176F88DD4910","a"
>
>>
:["91.219.236.218","80.255.11.213
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> You mean instead of:
>
> {"version":"2.3", "relays_published":"2015-04-25 18:00:00",
> "relays":[
> {"n":"shadowmourne","f":"1F515F1D420B498D9687658F4A3D176F88DD4910","a"
:["91.219.236.218","80.255.11.213"],"r":true},
>
>
{"n":"StinTheHuman","f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 19:58, nusenu wrote:
> Karsten Loesing:
That timestamp is updated as last step of the hourly update
>> process. The details documents that you're fetching may
>> have been updated before. That would also explain some
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Karsten Loesing:
>>> That timestamp is updated as last step of the hourly update
> process. The details documents that you're fetching may
> have been updated before. That would also explain some
> differences.
>>>
>>> Wouldn't it make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 13:44, nusenu wrote:
>>> If their 'relays_published' timestamp match, they processed
>>> the
same consensus, correct?
>> That timestamp is updated as last step of the hourly update
>> process. The details documents that you're fetchin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>> If their 'relays_published' timestamp match, they processed the
>>> same consensus, correct?
> That timestamp is updated as last step of the hourly update
> process. The details documents that you're fetching may have been
> updated before. That
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 12:44, nusenu wrote:
> Karsten Loesing:
>> These might either be bugs, or one instance was missing a
>> descriptor or consensus that the other instance was processing.
>
> I assume the instances do not process the same descriptors in
> ev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Karsten Loesing:
> These might either be bugs, or one instance was missing a
> descriptor or consensus that the other instance was processing.
I assume the instances do not process the same descriptors in every
case. That would explain most of the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/04/15 20:40, nusenu wrote:
> if I ask two onionoo instances running the same version (as given
> in the header of the document) for the same details document, to
> what extend should they match if relays_published matches, sorting
> is been taken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
other examples:
different views on when last_changed_address_or_port actually happened:
"A4877053906D36F47F0E610DC56E95601123C02A","last_changed_address_or_port
":"2015-04-13
14:00:00"
vs.
"A4877053906D36F47F0E610DC56E95601123C02A","last_changed_ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
if I ask two onionoo instances running the same version (as given in
the header of the document) for the same details document, to what
extend should they match if relays_published matches, sorting is been
taken care of and lets assume that both
11 matches
Mail list logo
