mp_en_viaje: keks, came to admire the http://logs.nosuchlabs.com/log/trilema/2019-10-03#1939873
snsabot: (trilema) 2019-10-03 asciilifeform: lobbes: if you want to emphasize that it's a mp-endorsed castle, put the deed in the chan subjline like in #a.
mp_en_viaje: good luck goodfolk!
shinohai: http://btcbase.org/log/2019-10-04#1940194 <<< maybe late to party, since you kicked the idlers ... but remember even w/ cloak users like those can /monitor <nick> and get you real ip no problem.
asciilifeform: probably
asciilifeform: as well as the other chans.
asciilifeform: shinohai: was moar curious to see whether they'd come back.
shinohai: Well they won't come back with +b, neh?
asciilifeform: come back from elsewhere/renicked, presumably.
asciilifeform: but yes, not deeply interesting.
shinohai user@usg.pro has joined #asciilifeform >.<
asciilifeform: lol
shinohai: Was wondering is this annoyance related to why I kept failing to d/l rockchip kernel from ur site yesterday?
asciilifeform: almost certainly why
shinohai: Tried twice, failed both times. :/
asciilifeform: http://logs.ossasepia.com/log , http://logs.ericbenevides.com/log , alive, can follow the story if you like shinohai
shinohai: kk thx, I was using btcbase in meridian since I failed to reach nosuchlabs or ossasepia.
bvt: just ftr, this was my idea re disconnect detector http://paste.deedbot.org/?id=sdmr ; i think there is no need in it with your mechanism in place
asciilifeform: bvt: the above is completely wrong. socket.timeout happens ALL THE TIME
asciilifeform: because it is how i get away with using a blocking socket at all, it times out regularly to no ill effect
asciilifeform: specifically did this, to make the bot unhangable
bvt: yes, but as long as freenode responds in time (has 30 secs for it), everything is fine
asciilifeform: bvt: possibly worx. but i'ma 1st try with mine.
bvt: the idea is to try sending a message (ping works), if send throws, connection is broken; if freenode can't respond, other node may work better
asciilifeform: bvt: absofuckinglutely NO asynchronous sends.
asciilifeform: this is how the old cl bot sucked.
bvt: it's definitely not async, but it guess i'd have to find the thread where cl bot was discussed to see what the issue was
asciilifeform: issue was that ANY sends by bot other than 1-to-1 to received, creates race condition.
bvt: it would be very useful to keep a strace of bot's irc front, hard to understand what is going on otherwise
asciilifeform: bvt: enable irc_debug
asciilifeform: then will get all the trace you can eat
bvt: not the same thing, but perhaps usable for the purpose; i don't like being separated by python's layers of abstraction from what actually happened.
asciilifeform: bvt: tcpdump/wireshark then
bvt: yes, that works