asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $64773.38
asciilifeform: !w poll
watchglass: Polling 17 nodes...
watchglass: 185.85.38.54:8333 : Could not connect!
watchglass: 84.16.46.130:8333 : Could not connect!
watchglass: 185.163.46.29:8333 : Could not connect!
watchglass: 205.134.172.26:8333 : Alive: (0.085s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706008
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.141s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706008
watchglass: 54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.111s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 205.134.172.28:8333 : Alive: (0.024s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=706008 (Operator: whaack)
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.143s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.163s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706008 (Operator: asciilifeform)
watchglass: 205.134.172.27:8333 : Alive: (0.145s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706008 (Operator: asciilifeform)
watchglass: 208.94.240.42:8333 : Alive: (0.216s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 54.38.94.63:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.264s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 143.202.160.10:8333 : Alive: (0.292s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 213.109.238.156:8333 : Alive: (0.332s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.595s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=706008
watchglass: 176.9.59.199:8333 : Violated BTC Protocol: Bad header length! (Operator: jurov)
watchglass: 192.151.158.26:8333 : Busy? (No answer in 100 sec.)
asciilifeform: welcome to the 700000s, folx...
shinohai: >.>
cgra: thimbronion: i'm looking at shinohai's publication of alcuin. Server.handle_udp_data()'s 'unknown peer' debug print wouldn't work, because string format args not as a tuple
cgra: thimbronion: (fwiw, likely not worth mentioning separately: could've also unpacked 'bytes_address_pair' tuple like this: "data,(ip,port) = bytes_address_pair")
asciilifeform: wb cgra !
punkman: "we built a new device called the Orb. It solves the problem through biometrics: the Orb captures an image of a person’s eyes, which is converted into a short numeric code, making it possible to check whether the person has signed up already. If not, they receive their free share of Worldcoin. "
thimbronion: cgra: noted, ty!
dulapbot: Logged on 2021-10-21 11:22:35 cgra: thimbronion: i'm looking at shinohai's publication of alcuin. Server.handle_udp_data()'s 'unknown peer' debug print wouldn't work, because string format args not as a tuple
asciilifeform: punkman: lol, fritzchip coin? (afaik not the 1st such, even)
shinohai: thimbronion: do you have a station currently operating I could connect to?
asciilifeform: punkman: dunno whether you followed the 'electronic cash' subject pre-bitcoin, but it was replete with idiocies involving 'untamperable modules' etc
thimbronion: shinohai: I can stand one up if you like. Gimme til the weekend tho - preparing for a trip and a bit swamped at the moment.
shinohai: kk thimbronion no worries.
cgra: noob question inbound...: why should a software author adhere to 80 columns?
asciilifeform: cgra: asciilifeform does 80cols where possible. reason being that asciilifeform uses 1) portrait-mode displays 2) printers
shinohai waits to see if Linus Torvalds throws brix @ asciilifeform for that statement ......
cgra: asciilifeform: do you use paper for book/binder output specifically only, or also office plastered with full source code, for a head-load process?
cgra: asciilifeform: re portrait-mode display, how many 80cols simultaneously, side by side?
asciilifeform: cgra: 1. asciilifeform doesn't like small print.
asciilifeform: cgra: for dead tree -- 3rings. also there's a 3x2m cork wall for loose sheets.
gregory5: I must admit that I am still attached to American conventions such as three-ring binders and letter-sized paper.
gregory5: I also prefer customary units to metric.
gregory5: There is just something more intuitive about having three bushels in a hogwash.
asciilifeform: gregory5: asciilifeform aint the least bit attached to furlongs-per-hogshead. or 3rings; they're simply what's commonly available here.
cgra: thimbronion: would you perhaps see value in converting 'message object as dict' into a py object in alcuin? would read 'message.command' instead of 'message["command"]' where 'command' highlighted as string constant (throws me off a bit, personally). also perhaps the attribute 'original' would get an explicit default value (tho not far enough in reading to understand whether default actually needed)
thimbronion: cgra: yeah it should probably be an object - didn't convert it yet because it didn't need any internal logic. At least I'm not just using multiple return values like I was before!
cgra: thimbronion: zeroed chain values ought to be '"\x00" * 32' instead of '"0" * 32'. the latter yields a '0000...' string, while ought to be a string of null-bytes
thimbronion: cgra: was wondering about that...
thimbronion: the hex representation looked off
cgra: asciilifeform: thinking beyond pest irc-like messages, is it too early to consider a spot to explicitly encode a message payload size? the actual text content is currently null-terminated, even if upper boundary is defined. say, i wanted to send a warez file. it's size is usually not going to be an exact multiple of pest message payload. and it could end in a string of null-bytes
cgra: (for completeness, in-between null-byte strings of a warez file also an issue similarly, cuz may coincide last bytes of a pest message payload)
asciilifeform: cgra: was gonna set aside a msg code for multipartisms (we might want to use e.g. signpost's luby transform, where 'part x of y' has very diff. meaning from the usual, say)
asciilifeform: cgra: imho the plain text msg format is exactly fine as it is (either the first null byte, or the end of the msg space, is the terminator, whichever comes first)
cgra: asciilifeform: is multipartism going to have a different message format?
asciilifeform: cgra: subformat
asciilifeform: (i.e. req's no changes to the format as-given thus far save for the addition of a command code )