1 2016-10-12 02:31:30 0|luke-jr|wumpus: eh, each issue is a thread.. not like anything else has much better?
2 2016-10-12 02:32:54 0|luke-jr|I mean, I guess email tracks each reply's parent, but too few email clients support that, and GMail (which is sadly popular) doesn't seem to do it right (if at all)
3 2016-10-12 10:30:48 0|sdaftuar|wumpus: achow101: #8499 still has some bugs that a few of us have been discussing offline, i'll update the PR with some comments
4 2016-10-12 10:34:45 0|luke-jr|sigh, downside of 64-bit: memory leaks are drastically worse >_<
5 2016-10-12 13:22:06 0|wumpus|back in the netherlands
6 2016-10-12 13:25:00 0|wumpus|luke-jr: I was thinking of a reddit-like nested structure, where replies appear under the post replied to, but making github mmore like reddit is probably bad mojo :)
7 2016-10-12 13:26:15 0|sipa|hahaha
8 2016-10-12 14:20:08 0|Chris_Stewart_5|Is CAddrMan used mostly by CConnMan to figure out what connections we should keep in our connection pool inside of CConnMan?
9 2016-10-12 14:24:15 0|sipa|and to decide who to make new connections to
10 2016-10-12 14:24:24 0|sipa|and to decide what responses to give to a getaddr
11 2016-10-12 14:28:11 0|Chris_Stewart_5|Is CConnMan just an abstraction of that to play nicer with our wallet?
12 2016-10-12 14:31:44 0|sipa|no
13 2016-10-12 14:31:50 0|sipa|connman manages connections
14 2016-10-12 14:32:12 0|sipa|it's the beginning of a refactor to abstract out all networking operations to one place
15 2016-10-12 14:32:35 0|sipa|also, connections have nothing to do with the wallet part
16 2016-10-12 14:35:00 0|Chris_Stewart_5|Yea, I was reading the CWalletTx code, and seeing how it uses those quantifiers to broadcast txs I guess
17 2016-10-12 14:36:21 0|Chris_Stewart_5|Is there any place people have written about the architecture of the networking stuff?
18 2016-10-12 14:38:25 0|sipa|it's very much in flux
19 2016-10-12 14:38:47 0|Chris_Stewart_5|Ok, thanks.