asciilifeform: $ticker btc usd
btcinfobot: Current BTC price in USD: $43403.32
asciilifeform: !w poll
watchglass: Polling 15 nodes...
watchglass: 185.85.38.54:8333 : Could not connect!
watchglass: 185.163.46.29:8333 : Could not connect!
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.087s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=672222
watchglass: 205.134.172.26:8333 : Alive: (0.082s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672627
watchglass: 108.31.170.100:8333 : (pool-108-31-170-100.washdc.fios.verizon.net) Alive: (0.098s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672627 (Operator: asciilifeform)
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.144s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=672627
watchglass: 205.134.172.28:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=672611 (Operator: whaack)
watchglass: 192.151.158.26:8333 : Alive: (0.086s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=672627
watchglass: 54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.173s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672493
watchglass: 208.94.240.42:8333 : Alive: (0.222s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=672627
watchglass: 143.202.160.10:8333 : Alive: (0.253s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=672627
watchglass: 213.109.238.156:8333 : Busy? (No answer in 100 sec.)
verisimilitude: I'm finally adding another command to my newer MMC design, MOVE, which simply relocates a block of memory, and which the previous design made less elegant.
verisimilitude: I've noticed that, while the whole is simpler with doubly-linked lists, some of the individual routines are much more difficult to write correctly.
verisimilitude: This is primarily due to the edge cases on either end, so I should see whether some alterations to my fundamental routines would alleviate these.