asciilifeform: most precious, 'As for WordPress, if your claim is that modern versions of WordPress are somehow less secure than older versions, that's also objectively incorrect, as shown by their release history and the number of fixes for security issues known to exist in older versions.' didjaknow !
asciilifeform reluctant to move www to piz, it's a fairly high traffic item, possibly adds up to half a trilema's (complete with regular ddosism)
asciilifeform: so there aint even to where send hate mail.
asciilifeform: motherfuckers removed all human support, also, 'unless pay subscription, 30 $ up-front + 5/mo'
asciilifeform put in what loox like a working workaround. if anyone sees barf , plox to write in. and will have to move the thing, i suspect, sooner than expected.
asciilifeform: sooooo... loox like all things die. and nfs hosting co finally went fullbore stupid. asciilifeform's www is hosed, they 'upgraded' php forcibly.
asciilifeform: ( funnily enuff , these same featured in the 'glove incident'. so occasionally 'in vivo' tested inadvertently.. )☝︎
asciilifeform: ( in some industrial applications -- actually do not know in advance. in usa there is a 'national library of compounds' , coupla million synthetic rubbishes that literally no one had even fed to amoeba, much less to man. at one time asciilifeform's work consisted of uncrating $compound-of-the-day and brute force testing in vitro. but afaik dope people do not work from 'library', but from old 'mature tech' . )
asciilifeform: i think even g_l folk know, roughly, in advance, what will be effect
asciilifeform: ( supposing 50% padding to payload -- this'd be 1024 bytes/sec of payload, i.e. quite enuff for a (compressed) voice conversation in realtime, say. )
asciilifeform: BingoBoingo: so wait, isidora was a pseudo-chix ?
asciilifeform: ( the typical g_l, as i understand, aint 'watchmaker elephant' , tho, but rather ordinary elephant. but this is possibly separate point. )
asciilifeform: chemist & ex-auschwitz fella primo levi had an essay, actually , re where errything a chemist does is 'elephant watchmaker' , i.e. 'blunt' manipulations which add up to desired effect on microscopically fine subject
asciilifeform: mp_en_viaje: imho the hammer analogy is poor, tho -- i've 'optimized cpu' with... grinder (polish heat sink), other folx -- with liquid n2, etc. 'barbaric' manipulation can in some cases optimize fine mechanism . for some value of optimize.
asciilifeform: girlattorney: the supposed 'need' is 100% manufactured psyop, yes.
asciilifeform: (it can be improved, potentially, but is very difficult to do without compromising integrity under concerted attack. and 'concerted attack' has been going 24/7 since late '14... )
asciilifeform: this is summary of why asciilifeform did not break back to try to optimize initial sync.
asciilifeform: girlattorney: there is not an escape from 'need wot'. consider, you had to get the proggy from somewhere.
asciilifeform: so the 6 or so wks the sync takes, in this timeline are not imho significant.
asciilifeform: girlattorney: my current personal node was synced from-empty in '17, and running 24/7 since. (prior -- dead ssd. prior -- another 2y of continuous operation.)
asciilifeform: ( often -- 0, people tend to stand'em up via eatblock )
asciilifeform: the other side of the medal, is that a trb node spends only small portion of its life in initial sync.
asciilifeform: the 'reject peers sending garbage' mechanism is also mine. trb did not always have it. i submitted it for inclusion to mod6's flagship after determining that it results in substantially improved performance across the board (i.e. peers sending bloomism are, statistically, an unlikely source of the-next-block)☝︎
asciilifeform: girlattorney: there is not currently such a knob. no one has felt pressing desire for it; if you wanna submit patch -- folx will read.
asciilifeform: ( not to mention, even when relaying actual bitcoin blocks & tx, blows gigatonnes of bandwidth on nonsense inserted by wreckers as prelude to their bigblockism scheme of '15 , e.g. bloomism )
asciilifeform: prb had 'orphanage' mechanism where it accepted antecedent-less inputs 'on faith'. this opens node both to memory exhaustion and algorithmic complexity attack (i.e. crafted input can prompt machine into wasting arbitrary amt of memory, + arbitrary amt of cpu cycle walking it)
asciilifeform: this includes e.g. a block whose parent was not yet seen; a tx whose antecedent input(s) not yet seen .
asciilifeform: girlattorney: 'discard excess' in trb algo is ANYTHING received when its antecedent is absent.
asciilifeform: girlattorney: 'core' (aka prb) when bootstrapping, asks randomly selected peer for 'headers' and eats'em on faith. afterwards does same with blocks (none of which it bothers to actually verify, in the traditional sense)
asciilifeform: answr to given puzzle is very simple -- most of the supposed btc net, consists not of nodes, but of equivalent to sand in engine's crankcase.
asciilifeform: girlattorney: simple logical inference (there's a number of publicly advertised trb nodes; most of'em agree with heathendom re the height) points to : no, not 'only with themselves' dunnit.
asciilifeform: girlattorney: will still be banned by any working trb node, on acct of sending nonclassical protocol cmds (bloom filter garbage etc)
asciilifeform: ( other half of problem is -- miners mining w/out actual working node. but this is elaborated in the logs, will not repeat )
asciilifeform: and 99,999...% of their cpu cycles spent rejecting rubbish from the 9000 'nodes' running nsaware.
asciilifeform: girlattorney: problem, as such, is that right now there are maybe two dozen btc nodes (actual, working ones, w/out segshitness etc) and most of'em belong to the folx here.
