verisimilitude: Now that I'm caught up with the messages, I'll also comment on the Chinese. I resolved to not bother trying to speak it, as even native programs include subtitles, given the many dialects; the intonation was further encouragement. Still, I've no intentions to ever visit, so reading in chat rooms or documents will be sufficient.
verisimilitude: My education has been very insufficient, so I'm nowhere near fluent. It was unpleasant to ask my instructor how some technical words are derived, to learn they're largely fabricated; English certainly has the advantage in this.
verisimilitude: I'm far more concerned with becoming fluent in Latin, Greek, and conlangs. I'd like to translate some of my articles to toki pona once I consider myself fluent therein, and then to other languages as I learn them. Now I wonder why loper-os doesn't seem to have Russian translations available, or have I merely overlooked these?
verisimilitude: Regarding the Naggum piece, I can't agree with backwards compatibility being valuable in computing, yet. Unicode has misspellings, because they couldn't be bothered to get it correct initially. HTTP is singlehandedly responsible for popularizing the misspelling of ``referrer''. UNIX was created by people who don't think programs need to be correct.
verisimilitude: To not discard with that would be akin to ``Okay, now that we've burned down the library, let's be civil from here on out and respect each other's ideas.'', and it would be disgusting.
verisimilitude: There are correct ways to do things, and so wrong ways, and most of computing is wrong, and so should be destroyed.
cgra: hi all, i've been a reader of anything tmsr related, is why i knew of this channel. i came here, because i might have something useful to say re trb sync issue.
cgra: it appears that trb's "chained sync" (like the initial sync) doesn't currently work, because it depended on originally buffering the bastard blocks. further details follow:
cgra: 1) chained sync is a repeating sequence of "getblocks" query, "inv" response, "getdata" query, 1+ "block" responses, and one last magic "inv" response advertising the most current block (see "pfrom->hashContinue" in the code).
cgra: 2) trb's chained sync stops right after the initial cycle, because "asciilifeform_orphanage_thermonuke.vpatch" got rid of "PushGetBlocks()" in the "inv" message handler: the node being behind doesn't react to the magic current block advert anymore.
cgra: 3) if parallel sync is desired, some kind of buffering must be reintroduced - perhaps just the block hashes the source peers advertise in their "inv" responses. i have no obvious fix to offer, i just wanted to get this out sooner rather than later.
cgra: the angle i'm looking at this, is specifically the initial sync. i have no experience of long term node operation.
cgra: ... i might have been too early in making conclusions, i need to learn more trb mechanics. i realized i don't really know enough about the subject yet.
cgra: back to trb school bench, but will follow the logs for a while.
trinque: cgra: hang around for a while as you investigate.
trinque: oh, ok.
trinque: ftr, I've seen trb take way longer to sync than prb clients, would be curious if there are ways to speed it up *without* compromising safety of operation.
shinohai: prb camp using "muh pruned nodes" now. :(
trinque: shinohai: sounds about right.
trinque: riffing a few bars more, listen, all that are tuned in, and were ever tuned in.
trinque: now is not the time for coyness, while the world descends into socialist idiocy, a great depression, and insane children-of-the-drug-addled.
trinque: if you have any urge to live left in you, get off your fucking ass.
shinohai: The socialist wave is indeed turning into tsunami nowadays.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020426 << except it ~does~ work, albeit slowly.
snsabot: Logged on 2020-08-25 07:46:58 cgra: it appears that trb's "chained sync" (like the initial sync) doesn't currently work, because it depended on originally buffering the bastard blocks. further details follow:
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020428 << first of all, PushGetBlocks is still there. and , after 'aggression' patch, also here .
snsabot: Logged on 2020-08-25 07:47:14 cgra: 2) trb's chained sync stops right after the initial cycle, because "asciilifeform_orphanage_thermonuke.vpatch" got rid of "PushGetBlocks()" in the "inv" message handler: the node being behind doesn't react to the magic current block advert anymore.
asciilifeform: 2nd of all, noshit it doesn't give a damn re 'current' block, because there is no way to verify it ! it is only possible to verify a block for which there exists an antecedent.
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020429 << i abolished the buffers quite deliberately, because they are a trivial attack vector. if yer node accepts unverifiable blocks, i can stuff its buffer full of liquishit, and effect on your end will be quite the same as having no buffer at all, but simply eats moar ram. (in early trb -- would in fact exhaust machine ram, because no mechanism to limit the buffers)
snsabot: Logged on 2020-08-25 07:47:22 cgra: 3) if parallel sync is desired, some kind of buffering must be reintroduced - perhaps just the block hashes the source peers advertise in their "inv" responses. i have no obvious fix to offer, i just wanted to get this out sooner rather than later.
shinohai: https://github.com/bitcoin/bitcoin/pull/4468 <<< lest you wind up with?
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020435 << thus far the only potential pill i've come up with is 'cement'. (i.e. noad eats a wot-signed list of block hashes, to then use during sync.)
snsabot: Logged on 2020-08-25 10:18:21 trinque: ftr, I've seen trb take way longer to sync than prb clients, would be curious if there are ways to speed it up *without* compromising safety of operation.
asciilifeform: any other approach to 'speed up sync' leaves you wide open to getting stuffed fulla randomly-generated garbage.
asciilifeform: because, elementarily, the only incoming block that can be verified is the very next one after the last that you have at any given time.
asciilifeform: ( or, in 'reorg' case, a higher-POW block succeeding N-kth, for small values of k )
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020421 << i might do a ru ver. of ffa at some pt. thing is, most cultured ru folx (just like fr, cn, etc) know enuff english to read technical lit. so i have not made translation a priority.
snsabot: Logged on 2020-08-25 01:28:50 verisimilitude: I'm far more concerned with becoming fluent in Latin, Greek, and conlangs. I'd like to translate some of my articles to toki pona once I consider myself fluent therein, and then to other languages as I learn them. Now I wonder why loper-os doesn't seem to have Russian translations available, or have I merely overlooked these?
asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020422 << entirely troo. however, note that historically, most 'let's break errything!' 'revolutionary' folx created pile o'shit entirely similar to the 'old regime' crapola.
snsabot: Logged on 2020-08-25 01:33:54 verisimilitude: Regarding the Naggum piece, I can't agree with backwards compatibility being valuable in computing, yet. Unicode has misspellings, because they couldn't be bothered to get it correct initially. HTTP is singlehandedly responsible for popularizing the misspelling of ``referrer''. UNIX was created by people who don't think programs need to be correct.
feedbot: http://peterl.xyz/2020/08/things-i-have-learned-about-setting-tiles/ << Blog of Peter Lambert -- Things I have learned about setting tiles
snsabot: Logged on 2020-08-25 01:34:58 verisimilitude: To not discard with that would be akin to ``Okay, now that we've burned down the library, let's be civil from here on out and respect each other's ideas.'', and it would be disgusting.
shinohai: asciilifeform: I am making mirror of gnatdeps, but for http://nosuchlabs.com/pub/gnatdeps/gmp-5.1.3.tar.bz2 I get eggog page.
shinohai: $uptime
btcinfobot: The bot has been up for: 1 days 3 hours 3 minutes and 35 seconds
asciilifeform: shinohai: will take a look, prolly typo
shinohai: tyvm
asciilifeform: shinohai: fixed (it's a .tar.gz, not .tar.bz2 )
shinohai: ah kk
asciilifeform: lemme know if any other similar.
asciilifeform encourages folx to make mirrors.
shinohai: I've been meaning to do gnatdeps mirror for some time, but anywho: http://btc.info.gf/devel/ada/gnatdeps/
shinohai: Will add signed manifest this afternoon.
trinque: asciilifeform: I was mostly trying to get the novice to be less cockshy
trinque: meh.
trinque: can't model on my end what's so great about netflix among the last-men
asciilifeform: trinque: re novices, it's pretty common to 'i just found this, and It's So Wrong! Here's How to Fix'. not damning per se imho, unless incorrigible. re netflix -- nfi. folx too lazy to dig for warez ?
asciilifeform: shinohai: nifty. the moar mirrors, the merrier.
thimbronion: asciilifeform: there is maybe one entertaining show per season on Netflix. Nothing to sustain daily viewing.
asciilifeform: thimbronion: i srsly wouldn't know, given as i dun subscribe to drmisms .
thimbronion: asciilifeform: nothing worth having your own copy of, to be sure.
asciilifeform: !w poll
watchglass: Polling 12 nodes...
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.082s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 205.134.172.26:8333 : Alive: (0.058s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.055s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 208.94.240.42:8333 : Alive: (0.166s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 192.151.158.26:8333 : Alive: (0.216s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 213.109.238.156:8333 : Alive: (0.335s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645315
watchglass: 188.121.168.69:8333 : (rev-188-121-168-69.radiolan.sk) Alive: (0.513s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 205.134.172.27:8333 : Alive: (0.664s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645316 (Operator: asciilifeform)
watchglass: 108.31.170.3:8333 : (pool-108-31-170-3.washdc.fios.verizon.net) Alive: (0.145s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=645316 (Operator: asciilifeform)
watchglass: 143.202.160.10:8333 : Alive: (0.149s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=645316
watchglass: 176.9.59.199:8333 : Busy? (No answer in 20 sec.) (Operator: jurov)
watchglass: 103.36.92.112:8333 : Busy? (No answer in 20 sec.)
asciilifeform: $ticker btc usd
btcinfobot: Current BTC price in USD: $11317.73
asciilifeform: 'round and round and round they spin, with feet of lead, and wings of tin...'(tm)(r)(k. vonnegut)
feedbot: http://mvdstandard.net/2020/08/us-federal-reserve-chief-to-announce-greater-tolerance-toawards-inflation/ << The Montevideo Standard -- US Federal Reserve Chief To Announce "Greater Tolerance" Toawards Inflation