asciilifeform: '"I am not happy with the dominance of Chinese contractors. In the first place, the money that they get from these contracts is externalised and all that they return here are meagre wages," said Edgar Syakachoma, himself a contractor. "Let the government also give us the contracts so that they benefit Zambians."' << hey, recall mircea_popescu's piece with the argentine anti-bus protesters

asciilifeform: ( classical btc 'thermodynamics', predispose to cartel. but 'kinetics' of ~randomsoup (vs 'intelligent' routing) make this less apparent. )

asciilifeform: !#s thermodynamics proposes kinetics disposes

asciilifeform: then again we may already be in the midst of just such a thing, there's, what, ~20k distinct nodes operating, and overwhelming majority of these, are simply rubbish

asciilifeform: and theoretically if the cartel births '9000' new sybils, it will force the use of something like my algo, whether anyone wants to or not, the layer of sibylade would become undrillable in its absence . but this is admittedly a stretch. ☟︎

asciilifeform: the fundamental problem is that the conditions favouring miner cartels are already baked into btc per se.

asciilifeform: but end result may end up being a net where even moar 'winner take all' than presently.

asciilifeform: Mocky: the current algo optimizes for nuffin at all. but the puzzler is, if we were to optimize for ~something~, could it create a problem. esp if the algo worx as i predict, and the nodes using it, end up forming an optimally short link to the miners.

asciilifeform: Mocky: recall the chains of empty/near-empty blox the chinese sometimes emit

asciilifeform: Mocky: the boojum is that mining in classical btc worx in such a way as to amplify small advantages into gigantic

asciilifeform: but on the other hand, the current system makes for pestilential sibylism.

asciilifeform: and not merely because A,B,C reliably supply correct blox, but they also will have most reliable tx-eating. so they will get sent all new tx in preference to D.

asciilifeform: thereby any peer ranking algo that favours 'useful' peers, will give A,B,C a substantial advantage over any new D.

asciilifeform: gedankenexperiment : let's suppose that all new blox presently are born in nodes A, B, C. from there, propagate to rest of planet. the immediate peers of A, B, C, will have them parked at the very top of their peer table, right below the manually-added 'meat' peers. now say a D shows up. D may have faster hash rate even than A+B+C, but his blox will still be considered only ~after~ those of A,B,C. at least, for a time.

asciilifeform: or, rather, slightly increases the 'inertia'

asciilifeform: i'd be interested to see what mircea_popescu makes of this algo. because i can see a possible fatal downside.

asciilifeform: ( nao, ideally all of the sane people would actually know one another and wot, and link their nodes via ciphered pipes, all the way to miner. but i dun expect to live to see this. )

asciilifeform: whatever machine cycles ~remain~ after this, can service randos.

asciilifeform: sanely-behaving nodes (both trb and hypothetical trb-compatible heathens, which exist, or we'd see 0 blox) ought to be able to find ~and keep~ each other company

asciilifeform: arguably 1st step to properly de-sibyl-ing the network.

asciilifeform: i suspect that it would lubricate both block rx and tx broadcast.

asciilifeform: imho a trb node ought to only advertise addrs that either a) part of the manual --addnode set the node was brought up with , or b) actually supplied a correct block in the recent past

asciilifeform: this presently consists 90+% of boxen that get immediately (or rather, not quite immediately.. http://btcbase.org/log/2018-09-23#1853265 ) malleus'd ☝︎

asciilifeform: mod6: right nao, our address-getting mechanism is the ancient turdalicious one inherited from shitoshi -- where the table is blindly filled with whatever connected folx decide to throw in

asciilifeform: mod6: my main hesitation re the item is that it may be 'plugging wrong end of funnel', quite possibly no such gymnastics would be necessary if we simply had a http://btcbase.org/log/2018-09-23#1853143 and always --addnode'd the actually useful nodes, rather than relying on pure chance ☝︎☟︎

asciilifeform: mod6: i was thinking of trinque's idea : suppose trb closed all open pipes if it finds that $configurable hours (e.g. 3) have passed without new blox

asciilifeform: diana_coman: traceroute --mtu destinationip will show the mtu of the 1st 'fraggable' node in the path ☟︎

asciilifeform: e receiver’s reassembly timer. For higher delay high capacity network paths, this limit of 65,535 packets in flight can be a potential performance bottleneck [RFC 4963].'

asciilifeform: in particular, 'Lost fragments represent a slightly more involved problem than lost packets. The receiver has a packet reassembly timer upon the receipt of the first fragment, and will continue to hold this reassembly state for the reassembly time. The reassembly timer is a factor in the maximal count of packets in flight, as the packet identifier cannot be recycled within the period defined by the sender-received path delay, plus th

asciilifeform: https://archive.is/ijjM3 << even moar pedantic detail re fraggism. ( can safely skip the ipv6-related crapola )

asciilifeform: ( this braindamaged design decision goes, as one might expect, back to the olden days when homo redditus was not yet on the net and 'arpa' designed for nukefest-related problems, not against 'ddos' ) ☟︎

asciilifeform: the other item of interest, not mentioned, is that quite a few infrastructural routers will simply drop frags, for the reason that all but 1 frag of a fragged packet contain no copy of the source or destination port -- and thereby impossible to ddos-filter. so they drop'em.

asciilifeform: ( can skip straight to section 'IP Fragmentation' )

asciilifeform: the 1 possibly noteworthy bit, is that fragging can take place anywhere in the route, while reassembly -- only at final receiver .

asciilifeform: diana_coman: https://archive.is/k6Wxb << udpism likbez ( may or may not contain anyffing new to you, but posting for the l0gz/n00bz )

asciilifeform: ave1: i was speaking generally, 'are there other hardwired pathisms in there'

asciilifeform: diana_coman: try the local variant. but i expect even across 1 router hop you will see similar picture.

asciilifeform: ( pleasant surprises are few and far between in the internet-of-shit )

asciilifeform: so far is exactly what i expected to see, aha

asciilifeform: diana_coman: i.e. there's a tiny reassembly buffer, and if it is occupied while new frags fall in, it drops

asciilifeform: diana_coman: it's consistent with what i know of the braindamaged frag reassembly mechanism on most iron

asciilifeform: the other simple experiment, re fragging, is to set up the receiver on local host, and then on same-lan box

asciilifeform: diana_coman: do you have a list of the ones that reached the other end ?

asciilifeform: diana_coman: tcpdump -i eth0 udp port YOURPORT -vv -X

asciilifeform: ( i long suspected that nothing far over 512, will reliably go ) ☟︎

asciilifeform: diana_coman: the other thing, entirely possible that yours got fragged and never unfragged, this'll be path-dependent ( as discussed in orig thread )

asciilifeform: according to the man pg, sento() block unless one were to set MSG_DONTWAIT ( and we didn't )

asciilifeform: diana_coman: unless i misread the docs -- yes

asciilifeform: diana_coman: iirc max packet that linux will actually send, is 65507 byte

asciilifeform: !Q later tell BingoBoingo crate seems to be in customs limbo still

asciilifeform: ideally in the end there will be none.

asciilifeform: ave1: pretty neat. curious, didja grep the whole thing for hardwired paths ? ☟︎

asciilifeform looks forward to test

asciilifeform: was dead end, tho, at least in the way originally written

asciilifeform: trinque: the crapola-gluetrap steadystate in trb is what i was trying to kill with 'wires' experiment

asciilifeform: http://btcbase.org/log/2018-09-24#1853486 << twist : turns out linus has 'intersectional-feminist'(tm) daughter, who helped to break him ☝︎☟︎

asciilifeform: this is an open problem. but there are some pretty simple things that still need doin', e.g. pill for http://btcbase.org/log/2018-09-23#1853265 ☝︎

asciilifeform: that we presently have no way to fully be rid of. is all.

asciilifeform: btw ( and this is not mega-revelation... ) 99.999..+% of noad traffic, is worse than useless -- box is speaking with noads who do not either bring it luscious next valid blox, NOR carry yer tx'en closer to miner, NOR even serve up full chain and enforce trad rulez thereon

asciilifeform: but i have not tested

asciilifeform: trinque: iirc ben_vulpes actually wrote an experimental this

asciilifeform: i've yet to see this 'stuck', aside from when actively verifying blox. if node with next block shows up, it goes.

asciilifeform: and otherwise happy to sit for 100 yrs talking to same fuckewits

asciilifeform: cuz it connects to diff nodes.