[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-dev] onionoo details document deterministic output
-----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":"7C05C5D24577CA4C3A904470AE5526C32290FCF0","a":[
"108.216.89.93"],"r":true}
> ], "bridges_published":"2015-04-25 17:52:43", "bridges":[ ]}
>
> something like this (note the "u" field):
>
> {"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,"u":"2014-05-25
>
>
18:39:15"},
> {"n":"StinTheHuman","f":"7C05C5D24577CA4C3A904470AE5526C32290FCF0","a"
:["108.216.89.93"],"r":true,"u":"2014-05-25
>
>
18:32:50"}
> ], "bridges_published":"2015-04-25 17:52:43", "bridges":[ ]}
Yes, one timestamp per record, but I'm not entirely sure what the
timestamps here represent. I expected more something like
2015-04-25 XX:00:00 (one hour granularity for consensus timestamps),
but not necessarily matching the one in the relays_published entry.
> However, I this is probably just a minor problem for most users.
> It's still a bug, but nothing too serious. (Your use case of
> finding differences between two Onionoo servers is probably the
> exception there.)
My use case will be
"feed details.json into a db once an hour and use relays_published as
the 'consensus timestamp' from which this data comes from".
But the assumption 'this comes from consensus X' is not valid in all
cases as we know. So I would use the per-record-timestamp to find out
on what consensus "I'm currently looking at" (in case something like
this will be added).
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVO/sDAAoJEFv7XvVCELh0pRsP/iaFADcKEK791d7cfW5FW+DH
hUAmwht91MUlwr1Tjj86ASjwedWexQh9w+jGlFqVi0Wm93eNxV+4XasW56OvIxs1
DlJ1Y1PtAIjqz+GxZdI8BDd6enQk6XCefoIV9FEWQrjp2qtYoVkKVDsdjR5nV7Vz
Basdr357QCmAPRMArhSp4Z1DrJ4wcZ2/v/FmkE24PaEIzS9Z5Yt7Y3cgk62JKM16
L7r+Vzz7Ss9Ad2xS0ry6SP3FtHlrTQ2mIKffwaAm3+dOBgYiyPvkP1T30CsVlDvy
RDB6G/iuotZGZkJIQGq4LasQhw8c4VMPK2lg1koLPJFKgGyR60DTxhP9TEObssNp
iRb3PPaELuuAhj5NxyndARRVsCmr8FuXYMhHwG7YevQh1DkNdTqox4AWgvTRO6Bd
Ai2fy1X8K5Xg/Rca2/Es2P7FTktHgd64wH6FnFU0NpTWRCS/VGV0SOULDr22D7OJ
ytXRAa5kYvIVzi0sdXr1jmB3Don4TVyogT97hRurbYYcooWlwqTGBaB/seacT48C
4RuryUjv4bGoP6U7M9xjeENkXcjzPX1KlJ3pPHsIAgQs9YKVvarLfU9EgdUFFA8q
BgKKm0q0diii0LiWW2kTEoAKzcIZZKD/9WD4BqZlWhFLg0PpvodpuhPrivbXfbZj
ZaOvhS4FPq9JGgEkoHPu
=Vh+R
-----END PGP SIGNATURE-----
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev