awt[asciilifeform]: $ticker btc usd
busybot[asciilifeform]: Current BTC price in USD: $21677.29
awt[asciilifeform]: 9972 sig: includes address cast support and a fix for the bug in which long messages are truncated instead of broken up into smaller messages.
asciilifeform: oh hey neato awt
asciilifeform will test as soon as hands free
awt[asciilifeform]: aweso
awt[asciilifeform]: me, thanks
awt[asciilifeform]: Last message types to implement (for blatta) are key offer and key slice. Honestly would wrather implement some kind of file storage/retrieval message types first.
asciilifeform: '# if the signature checks out for a peer with no AT entry, decrypt' << is this comment accurate, i.e. only worx if there is no at entry at all? (or worx per spec on any 'cold' peer?)
awt[asciilifeform]: No that comment isn't accurate. It checks all peers with keys.
awt[asciilifeform]: Actually doens't exclude warm peers though
asciilifeform: aok
asciilifeform: (oughta exclude warm peers tho)
asciilifeform: decoding against warm peers only wastes cpu
asciilifeform: ( a warm peer, logically, at that moment knows yer addr/port and won't be firing off addrcast )
asciilifeform: awt: does your latest blatta answer prod's correctly ? ( wasn't obv. to asciilifeform from reading the patch . the specful behaviour is that if receiving a prod where flag==0, one answers with anuther prod where flag==1. otherwise not answers)
awt[asciilifeform]: asciilifeform: it does
asciilifeform: awt: a++
signpost[asciilifeform]: awt: fired it up, getting a spray of error log messages regarding a peer with duplicate address or handle id.
signpost[asciilifeform]: it's complaining about deedbot and crawlerbot
signpost[asciilifeform]: which have neither the same address in AT nor same handle
awt[asciilifeform]: signpost: I left that message in there as more of a warning. I believe the duplicate check was needed due to an earlier error in the way at entries were created, where handle ids would be almost randomly assigned
awt[asciilifeform]: If there are no dupe values in your AT, I'm not sure why tha warning is firing off
signpost[asciilifeform]: filling up my logs atm with multiple per second
signpost[asciilifeform]: there are not. gotta be a bug in the is_duplicate thing
signpost[asciilifeform]: firing for deedbot still even though I unpeered crawlerbot
awt[asciilifeform]: feel free to comment it out, won't harm anything, but would be interesting to know specifically how it's borked
signpost[asciilifeform]: dropping some print statements in
awt[asciilifeform]: I am seeing ac messages from you btw
signpost[asciilifeform]: gird thine autisms for some noise while I debug plz
signpost[asciilifeform]: k the message originates from State.get_keyed_peers
signpost[asciilifeform]: and indeed deedbot has two keys in the keys table.
awt[asciilifeform]: Ah hmmm ok
signpost[asciilifeform]: deleting the unused key solved the warning message
signpost[asciilifeform]: not sure how I ended up in that state. I see that deedbot's sqlite db also has a duplicate key for bitbot
signpost[asciilifeform]: cool, going to update deedbot's station onw
signpost[asciilifeform]: *now
awt[asciilifeform]: It should be ok two have more than one key for a peer, but having duplicate keys is a little weird
awt[asciilifeform]: So get_keyed_peers still needs some work.
signpost[asciilifeform]: !!help
signpost[asciilifeform]: cool, those are on latest now.
signpost[asciilifeform] back to painting a room, bbl
awt[asciilifeform]: sweet
asciilifeform: awt: ideally thing oughta check for duplicate keys on startup (or prohibit'em entirely in sql schema, better)