-----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"],"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).
https://trac.torproject.org/projects/tor/ticket/15848
All the best, Karsten