sina: mod6: heya, not too bad, working on a gossipd impl!
sina: been working on it all week really
sina: its not finished yet, but I just completed the "server" portion of the daemon the next piece is to start on the "client" that connects to peers, generates RSA keys, sends bogus challenges
shinohai applauds sina for not writing it in golang ....
sina: shinohai: I was definitely thinking about it. there is a lot to be said for the strong typing and forced error checking which makes the program more robust
sina: anyway I am hoping to have a decent complete implementation done by tomorrow-ish
sina: I need to complete the client part for that so I can flesh out the key handling
trinque: what you've got there looks like a tcp-gpg-wad hucker
sina: I'm working on the spec per the blog post, the thread had a lot of stuff on which there wasn't a consensus yet
trinque: cool, was just curious which gossipd you meant.
sina: trinque: is there anything from the thread you think was agreed that materially modifies the spec in post? I figured mp would have updated if so
sina: going to get some food and chill out for a bit, any feedback would be appreciated
trinque: there was for example the lighthouse concept; asciilifeform has also spoken of using the luby fountain algorithm over iirc either udp or raw IP packets.
trinque: guy can speak for himself, but I'm sure these items await his "P"
trinque: doesn't prevent anybody else from fiddling in his own shop
sina: ah yeah I do remember reading the lighthouse comments
sina: trinque: my problem is I don't have an original bone in my body, so short of a well described (enough) spec I have a lot of trouble
sina: my impl is more "hey, here is a spec I can implement for some funtimes" than "hey, here is a useful thing"
sina: just going through those comments again trinque, e.g.
http://trilema.com/2016/gossipd-design-document/#comment-119015 "One possible cut of the Gordian Knot re: my "enemy's ability to trigger a response from a suspected-node on demand" would be for every node to have a "lighthouse" - an always-on broadcaster of authentication challenge strings." per the spec I will be implementing this
sina: "Unsolicited challenge strings will also be sent, at intervals and to destinations specified by the operator."
sina: although tbh I don't fully understand the purpose because if someone is watching the wire, they will see the session never gets fully established
jhvh1: BingoBoingo: Bitstamp BTCUSD last: 2703.83, vol: 8180.10512074 | BTC-E BTCUSD last: 2657.199, vol: 3153.9575 | Bitfinex BTCUSD last: 2688.5, vol: 7827.96099297 | BTCChina BTCUSD last: 2891.834538, vol: 5663.30470000 | Kraken BTCUSD last: 2682.525, vol: 3123.89985527 | Volume-weighted last average: 2729.98805555
jhvh1: shinohai: The operation succeeded.
shinohai: (also appears I forgot to close the SFYL tag with </a>)
erlehmann: safe, sane, consensual (choose max. 2)
shinohai: Alo BingoBoingo in your "Violence Today" piece ... s/is still after/is still at
shinohai: A "we did it reddit" occurred when Coinbase announced they will be making ppl that called on the ETH crash whole, but not really qntrable.
shinohai: Ah ha! Well, terms and conditions *do* apply it appears.
BingoBoingo: shinohai: That was on Qntra last year, except for the Arkansas ban part. good find, will qntra