log☇︎
59700+ entries in 0.014s
asciilifeform: ( and may have to be turned into a toggle knob )
asciilifeform: it is possible that it will improve block reception at the expense of outgoing tx propagation.
asciilifeform: aha
asciilifeform: exactly like what an unpatched trb does for first hour or three of boot
asciilifeform: well right nao it's pulling blox from other trb's, at ~100% efficiency
asciilifeform: mircea_popescu: right, idea being that it is conceivable that 'aggression' increases isolation . i cannot yet rule it out.
asciilifeform: and speaking of this, can haz patch that logs ~from what kind of node~ each ACCEPTED block came ? ( or do i have to do errything meself..? )
asciilifeform: ... as mircea_popescu prolly intuited , it remains possible that 'aggression' takes the trb<->prb link breakage from , say, the 80% of before, to 100% , and i would not learn about it until reaching tip.
asciilifeform: ( supposing ben_vulpes et al , dun report sooner )
asciilifeform: in ~1wk i expect to learn how it behaves at tip.
asciilifeform: almost like it were 2012 again...
asciilifeform: thing's been purring along, incidentally, at almost 100% blockverificationdutycycle, for most of a day nao.
asciilifeform: this'd matter moar in practice if 'aggressive' node saw many bastards . but it now sees very few, because immediately pushgetblocks() when it gets visited.
asciilifeform: , 2 ) disconnect from him )
asciilifeform: ( unrelatedly, but before i fughet, observation : http://btcbase.org/log/2017-12-21#1755826 i.e. bastardry handler, is unproductive because it asks 'fill in what we're missing', but 99 out of 100 shots, that's ~another~ bastard. really instead it ought to either 1) send a normal pushgetblocks() to the bastard-emitter , asking him for the ~one and only block we won't reject~, it being the immediately-next-one-after-our-topheight , or ☝︎
asciilifeform: well-known episode aha
asciilifeform: http://btcbase.org/log/2016-04-11#1450220 << thread ☝︎
asciilifeform: !#s societal security
asciilifeform: see also :
asciilifeform: there remains the possibility that it was not, yet, in the l0gz...
asciilifeform: ^ recurring thread
asciilifeform: !#s from:mircea_popescu nothing happen
asciilifeform: from pov of committee chair-warmer, 'something happening' is as desirable as an out-of-ordinary day at nuke power station
asciilifeform: kurchatov could strike a gentleman's understanding with stalin. but would have 'snowball's chance in hell' against a committee.
asciilifeform: it also only works where you have a throne room. would do 0 against a fungus.
asciilifeform: it pertains.
asciilifeform: mircea_popescu: aha. sorta why i retell it nao.
asciilifeform: then next wk 'tell us who is trying to be philosophical, and getting in the way...' ☟︎
asciilifeform: s replied 'bomb'
asciilifeform: kurchatov, supposedly, sat and thought, and few minutes later answered, 'perhaps from philosophical pov this'd be consistent. but then we will have to forget about obtaining the bomb.' ☟︎☟︎☟︎☟︎☟︎☟︎
asciilifeform: stalin summoned kurchatov to the throne room, and described to him 'we're gonna have a cleanup, in physics, like in genetics, what do you think'
asciilifeform: there was a specific conversation, legendarily:
asciilifeform: and very muchly under stalin.
asciilifeform: kurchatov was able to work in conceptual sphere, and not only without interference but with offer of 'tell us who is getting in the way, he'll be gone next morning'
asciilifeform: but i did say ~under~ stalin, not 'by'
asciilifeform: it's a stretch, conceptually, sure
asciilifeform often tries to picture what kind of software would have been written under stalin, if there had been on-what
asciilifeform: cargocultism?
asciilifeform: whip has curative power but apparently wasn't enuff for, e.g., microshit
asciilifeform: it is theoretically possible to write a correct module, but prolly not by homo-phpicus.
asciilifeform: aha!
asciilifeform: ( and can't simply use the html escape notation, because it gets literalized by the code-formatter )
asciilifeform: well how would it dwim. gotta offer an explicit escape. and the thing, apparently, doesn't.
asciilifeform: author, apparently, did not give it any ability to distinguish 'standalone double-quote because actually need it' from 'idjit user forgot to close the " '
asciilifeform: ( being a code formatter, it naively insists on colouring the inside of the double-quotes... )
asciilifeform: the as-is incurably kills it, because unpaired quote.
asciilifeform: i'ma prolly have to rewrite the code-formatter plugin thing, it insists on autoprocessing to emplace the escapes, but does not do ~mismatched~ double-quotes
asciilifeform: err, >
asciilifeform: < , <, & , did not have to uniturd, there are ready-made escapes for these
asciilifeform: took a bit of massage to get it to stop mutilating >, <, &
asciilifeform: mircea_popescu: this one isn't a wp problem per se, it's interaction b/w wp and the colorizer thing
asciilifeform: the current test on zoolag, however, is mighty interesting: after floundering in a sea of prb for ~hour, thing's been loading blocks almost continuously. at this rate will actually sync in a week or so.
asciilifeform: ( naturally , this is not a Troo Rigorous test. that'd go as i described, 2 identical, save for 'aggression', boxen, on 2 identical pipes )
asciilifeform: in other noose, 'aggression' patch is apparently ~the~ pill against what ailed zoolag; 482253 -> 484621 in ~12hr , previously that was 3-4 day's worth
asciilifeform: http://btcbase.org/log/2017-12-24#1757839 << this is pretty neat idea ☝︎
asciilifeform: ( i.e. nothing ~inside~ the vpatch, suffers )
asciilifeform: ^ this in re: to the ~www~ text strictly !!
asciilifeform: http://btcbase.org/log/2017-12-24#1757842 << the wp 'code' plugin is massive headache, i've been fighting it since ch1 . ( e.g in ch4 i had to replace the " in ('"') with a similar-looking uniturd, because double-escape is apparently impossible ) ☝︎☟︎
asciilifeform: congrats to phf , the 1st winner of ch4 puzzler.
asciilifeform: ty phf !
asciilifeform: they have a , what, 32byte slot allocated for the output of 'find out' ..?
asciilifeform: can't say that i am, shinohai
asciilifeform: neur0: http://btcbase.org/log
asciilifeform: neur0: consider reading the logs ?
asciilifeform: neur0: clock's ticking
asciilifeform: !!up neur0
asciilifeform: ben_vulpes, mod6 , phf , apeloyee, diana_coman , PeterL, all ffaists : ^ ptronic puzzle included! gentlemen, start yer engines...
asciilifeform: !~later tell phf >> http://btcbase.org/log/2017-12-24#1757748 << plox to snarf vpatch ☝︎
asciilifeform: https://ss64.com/bash/tsort.html << subj x2.
asciilifeform did not use it in vtron, because insufficiently illustrative
asciilifeform: http://btcbase.org/log/2015-09-01#1258158 << subj ☝︎
asciilifeform: !#s tsort
asciilifeform: aaactually...
asciilifeform: like it were 1941
asciilifeform: usa 'restaurants' are getting , slowly, to where folx will be carryin' folding forks in their boots again
asciilifeform: keccak is a req'd util , lives on the box
asciilifeform: why does it have to ship ~with~ keccak
asciilifeform: takes cmdline arg for standalone hasher.
asciilifeform: i.e. vtron not married to a hasher.
asciilifeform: who said 'support sha2'. said : 'programmable hash knob'
asciilifeform: if vtron dun know about it, it's as good as gone
asciilifeform: otherwise it gets repeated.
asciilifeform: tools get updated, idiocies removed, etc. but the HISTORY gotta stay.
asciilifeform: but dun... revere it
asciilifeform: i have a flounder , bought at bucharest flea market, preserved in epoxy like mircea_popescu's kindergartener
asciilifeform: forget revered
asciilifeform: a vtron ought to have programmable hash knob.
asciilifeform: the constant and entirely unnecessary reset of history is imho urbit-like and a Bad Thing. e.g. polarbeard ain't coming back to regrind his patches, nor is punkman
asciilifeform: trinque: i'd especially luvv a depythonized and deperlized one
asciilifeform: if yer surrounded by ocean of prb, it does 0
asciilifeform: i didn't either, for 1st hr or so
asciilifeform: lolk
asciilifeform: the correct, Troo , algo, is the one used in phf's vtron.
asciilifeform: ben_vulpes: http://btcbase.org/log/2015-11-14#1323387 is terribly, horribly wrong, disregard. ☝︎
asciilifeform: ^ achtung, panzerz !!
asciilifeform: (close to theoretical max sync rate on the given box)
asciilifeform: so far i'm getting surprisingly good result
asciilifeform: so far seems to be.
asciilifeform: ftr 'aggression' is apparently paying off, 200blox caughtup in <1hr, which previously took 4-5hrs (in the 400k's, to be specific)
asciilifeform: was 'too cheap to meter' (tm)(r)