log☇︎
14 entries in 0.496s
a111: Logged on 2017-08-05 21:11 asciilifeform: zoolag live as of now at ye olde 108.31.170.49 .
asciilifeform: !~later tell mod6 >> http://btcbase.org/log/2017-10-03#1719958 << plox to remove the deceased dulap, 46.166.165.30 . and also note that 108.31.170.49 ( zoolag ) is at 382k and will remain useless as a public node for some weeks. ☝︎
a111: Logged on 2017-08-22 21:35 mircea_popescu: ftr, only a coupla of those five actually work. i can connect to 46.166.165.30 regularly but can not connect to eg 108.31.170.49
a111: Logged on 2017-08-05 22:43 mod6: <+asciilifeform> zoolag live as of now at ye olde 108.31.170.49 . << thanks for the update.
mircea_popescu: ftr, only a coupla of those five actually work. i can connect to 46.166.165.30 regularly but can not connect to eg 108.31.170.49 ☟︎
mod6: <+asciilifeform> zoolag live as of now at ye olde 108.31.170.49 . << thanks for the update. ☟︎
asciilifeform: zoolag live as of now at ye olde 108.31.170.49 . ☟︎
asciilifeform: thestringpuller: http://btcbase.org/log-search?q=108.31.170.49
thestringpuller: zoolag : 108.31.170.49 << for future reference :P
thestringpuller: asciilifeform: I'm not Batman - http://btcbase.org/log-search?q=108.31.170.49 - how am I to make such a deduction?
asciilifeform: thestringpuller: 108.31.170.49 for quite a while now
whaack: ./bitcoind -connect=108.31.170.49 -nolisten -maxconnections=1
mircea_popescu: whaack how do you run it, something like -connect=108.31.170.49 -connect=54.187.227.228 -connect=46.166.165.30 -connect=91.218.246.31 -connect=172.86.178.46 -connect=50.168.67.12 ?
mircea_popescu: incidentally, what's the current list of public trb nodes ? i have -connect=108.31.170.49 54.187.227.228 46.166.165.30 91.218.246.31 172.86.178.46 50.168.67.12 of which a coupla be answering.