[tor-dev] onionoo details document deterministic output

[Karsten Loesing]

-----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 fetching may have
>> been updated before.  That would also explain some differences.
> 
> Wouldn't it make sense to mention/use the timestamp of the
> consensus that has been used to generate the output instead then?

It *is* the timestamp of the consensus that has been used to generate
the output.  But generating the documents that go into the output is
not an atomic step.  It's an hourly cronjob that runs for 15--30
minutes and writes documents for all relays to disk, and only after
that is done, the relays-published timestamp is updated on disk.  As
I'm saying on one of the tickets, one way to change this would be to
use a database and update all documents in a single transaction, but
that's a major change to the current design.  Which doesn't mean we
shouldn't do it, but it's not trivial, and maybe it's not the most
pressing missing feature.

Want to run your own instance of Onionoo and help develop it?  If you
need a host for that, we might be able to solve that somehow.

All the best,
Karsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJVO5ZMAAoJEJD5dJfVqbCrJpwH/i1yIhcjh+s4zc/NKrasmScH
mHEPBMXJ9+EHoiOx86X1enFoafgaEmFAiR7HdelabilTh7/sKhyMpSf51/WukLti
zd8+Ln200HO6nISVbV62XuLFliTOm63PvBi/mGKw/g+jIEvsxUVhwcMtYYBtBaqD
W44Y0La9T6YV//AChBLVeLOYy3NKFEf2nGD8vMlZd7GvhIVfDg2v1e4K7wCQwUsb
oaKI2HSxhBlqkn0EDTUyh0EH/FNMYYDeq2KbmkssCbQXfJUuJVJnwwA3JRs4vfdz
CoMNz5wW87KSgrfRRd/xWFKuwFu5tZJ9AGUPOU5FM/xuFAeJaCW/D/L180FRHOA=
=7Lud
-----END PGP SIGNATURE-----