Bryan Bishop
Bryan Bishop
Still relevant.
As an example, at the moment I don't see any commit messages sent into channels. I also don't see any bots logged on. I am using freenode and another no-name...
Huh, some of the commits got sent multiple hours later. Maybe there can be a blurb about a delay existing? I didn't even know.
Ah cool, thanks for the update. Yeah, maybe messages delayed for more than 6 hours (or some other number) should be modified to mention the delay? I'll consider digging in...
This doesn't seem to do quite what I want (serialization problems): ``` diff --git a/otsclient/cmds.py b/otsclient/cmds.py index 84c3b19..51ccf05 100644 --- a/otsclient/cmds.py +++ b/otsclient/cmds.py @@ -505,6 +504,15 @@ def info_command(args): print("Timestamp:")...
An efficiency gain is implemented in #109 (runtime cache to avoid multiple checks against calendar servers for the same commitment) but this is not entirely incompatible in concept with changing...
Alternative solution: always use `gt commit` and then sign with `git commit --amend -S`.
Just realized this is a dupe of #29
Can someone spot check this commit I made? https://github.com/petertodd/python-bitcoinlib/commit/e311d27edfd8df40e4457934178113c482e6cb8d
Also, why four bytes for the message length, instead of the VarInt or CompactSize that bitcoin uses? Is this meant to be some sort of explicit deviation from what other...