Peter Todd
Peter Todd
I'm inclined to keep the == stuff as a verbose option; I use info all the time to see how a timestamp was made, but almost never need to know...
@dhimmel Bitcoin uses a non-standard little-endian display for digests; try reading 8a1b66ecb7cbd07d8139a7e7d7f2c41aab1f5009b8364aaf61d03ad245e47e00 backwards. :)
I think that confusion is the kind of thing that should be explained in the documentation. Which speaking of: we need to write up at least some man pages, and...
Thanks! Looking forward to #103
@midnightmagic What specific problems are you having with the git support? I personally use it for repo's with tens of thousands of small files in them with no issues; remember...
Have you tried git-annex? You might find that it works better than pure git.
Have you checked out https://github.com/opentimestamps/python-opentimestamps yet?
Sorry, just noticed this! Yes, we should probably have upgrade always try to get new attestations for everything, regardless of whether or not we already have attestations. Along those lines,...
In principle yes, but actual software support for that isn't done yet. Note that you can verify manually: the client will tell you what block height the timestamp was for,...
Sure, that's fine. It can be part of your #103 pull-req; doesn't need to be a separate pull-req.