cgra: http://logs.nosuchlabs.com/log/asciilifeform/2021-12-05#1068777 << what i was contemplating here, was not out-of-order reception of blocks, but the opposite: fix the last out-of-orderism the old 'getblocks, sometimes mixed with new top block adverts' mechanism has. and prevent getting stuck while catching up, because of some block ending up barred by every peers' [http://cgra.net/2021/12/trb-defect-exhibition-oom-and-other-spam#
dulapbot: Logged on 2021-12-05 16:28:18 asciilifeform: cgra: by design, the only block a trb node can ever meaningfully process, is the 'next' one, whatever it happens to be.
cgra: setInventoryKnown]["spam guard"]
asciilifeform: cgra: hm. plox to detail proposed algo, then. (and how it'll behave when talking to an unmodified trb-compat. noad)
asciilifeform: afaik currently all (incl. prb) noades throw their 'latest' block at all peers; so yer stuck processing (often enuff, if node not fully synced -- expensively rejecting) it
cgra: asciilifeform: i'll just make a blog piece of this too, sometime soon(ish)
asciilifeform: cgra: ty, looking fwd to reading
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $48838.11
asciilifeform: !w poll
watchglass: Polling 14 nodes...
watchglass: 22.214.171.124:8333 : Alive: (0.021s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=712843
watchglass: 126.96.36.199:8333 : (172-6.core.ai.net) Alive: (0.090s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=712896
watchglass: 188.8.131.52:8333 : (ns562940.ip-54-39-156.net) Alive: (0.112s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=712896
watchglass: 184.108.40.206:8333 : (172-4.core.ai.net) Alive: (0.082s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=712896
watchglass: 220.127.116.11:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.093s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=712896 (Operator: asciilifeform)
watchglass: 18.104.22.168:8333 : Alive: (0.083s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=712896 (Operator: whaack)
watchglass: 22.214.171.124:8333 : Alive: (0.155s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=712896 (Operator: asciilifeform)
watchglass: 126.96.36.199:8333 : Alive: (0.204s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=712896
watchglass: 188.8.131.52:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.254s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=712896
watchglass: 184.108.40.206:8333 : Alive: (0.343s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=712896
watchglass: 220.127.116.11:8333 : (static-82-79-58-192.rdsnet.ro) Alive: (0.260s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=712336
watchglass: 18.104.22.168:8333 : (terebe.ns01.net) Alive: (0.601s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=712896
watchglass: 22.214.171.124:8333 : Could not connect!
watchglass: 126.96.36.199:8333 : Violated BTC Protocol: Bad header length!
PeterL: asciilifeform: happy belated birthday, saturday was my youngest daughter's birthday too (she's now 6)
asciilifeform: ty PeterL
asciilifeform: (bday theorem!1111)
PeterL: something like 30 people will probably have a birthday collision?
asciilifeform: iirc ~30 with p(0.5)
bitbot: (pest) 2021-12-06 asciilifeform[billymg]: jonsykkel, awt : hash is over ~entire~ field, not simply the portion prior to terminator
PeterL: http://logs.nosuchlabs.com/log/asciilifeform/2021-12-06#1068835 << asciilifeform: maybe I am missing something, but shouldn't tip-of-chain blocks get thrown out pretty quick by just not having their preceding block, why is it so expensive to process them?
dulapbot: Logged on 2021-12-06 09:34:56 asciilifeform: afaik currently all (incl. prb) noades throw their 'latest' block at all peers; so yer stuck processing (often enuff, if node not fully synced -- expensively rejecting) it
bonechewer: Belated happy birthday, asciilifeform!
bonechewer: Today's decline-of-the-USD-economy nooz: "they list parts they don't have, at prices they're not actually willing to accept"
asciilifeform: ty bonechewer
asciilifeform: 'do you have fish?' 'this is a butcher shop, here we don't have meat, fish is what they don't have at the fish counter' (tm)(r)(su)
asciilifeform: '...and the XC9572XL CPLD, and both of them now have limited or no supply' << RIP folx who wanted to bake verbatim FG knockoffs, apparently
adlai: it's unfixable by now, although the previous day's log page contains a broken link due to IRC message fragmentation (specifically, the link to cgra.net for the text "spam guard")
adlai: I'm uncertain whether there is any reasonable action item from that specific failure; that exact pattern is detectable by the log server, and all that remains is convincing myself that such automated detection-and-fixing is not unreasonable.
adlai: verisimilitude: the conversation didn't cease, it was "only resting"... I was even still connected to dulapnet, only parted from the channel.
adlai: wrt birthdays: for some reason, the magic number that I recall is 23, not ~30... sure, these are same OOM in base decimal, give or take a hand, although I wonder whether my mind plays tricks again.
adlai: the heuristic which I recall is that you can expect a 'Birthday Collision' somewhere around (sqrt (length sample-space)) samples; for the solar year, this is slightly over 19.
adlai: in other yakshaves, I wonder what convention to adopt for parenthetical remarks, given that I prefer to reserve #\( and #\) for lisp code, and it could be seen as excessive overloading to use them for both code snippets, and parenthetical remarks; easiest unknotting is simply, "do not make parenthetical remarks; either speak, or don't."!
verisimilitude: I referred to the email conversations, adlai.
verisimilitude: http://logs.nosuchlabs.com/log/asciilifeform/2021-05-19#1036887 https://github.com/nineties/planckforth
dulapbot: Logged on 2021-05-19 14:24:35 snsabot: Logged on 2020-07-18 19:55:54 asciilifeform: trinque: since you mentioned script langs: considering, after ffa, to attempt a 'dethompsonizing' simple gc-less scheme in asm, in style of 'M' as a scripting lang. can't speak for erryone, but i've wanted a <32kB scripting lang that 'compiles with bare hands' for many yrs.
verisimilitude: I've become increasingly convinced over the past few months that programming is best done with as little computation as feasible.
verisimilitude: Computation is disgusting where unnecessary.
verisimilitude: I refer to tables.
verisimilitude: As a very basic example: Consider comparing an integer to a static limit, without using a comparator.
verisimilitude: Consider an octet; the problem could easily be solved by a bit-table for each value.
verisimilitude: However, suppose the limit is high.
verisimilitude: Suppose it be noticed the first four bits must be one for the limit to be plausibly hit.
verisimilitude: Well, that enables a sixteen-entry table conditionally used with a few ANDs.
verisimilitude: That's arguably nicer.
verisimilitude: It uses the square root of the space of the former table solution.
verisimilitude: I want to program with tables and simple composition rules everywhere.
verisimilitude: Tables give the ability to easily review and dynamically modify a running system, as well.
verisimilitude: Why have opaque functions over tables, where unnecessary?