Forum logs for 01 Aug 2019
| mp_en_viaje: | BingoBoingo, nice | [02:59] |
| mp_en_viaje: | btw, i got like 60 pingbacks from you, that are all dupes. i mean... http://trilema.com/2013/ripple-the-definitive-discussion/#comment-95245 exists, but now theres also one from http://bingology.net/2013/09/26/anti-bitcoin-bitcoin-apps-part-3-gliph-in-particular/?b=Rippl&e=#select | [03:00] |
| mp_en_viaje: | i wonder wtf shall i do | [03:00] |
| mp_en_viaje: | lobbes hmm lobbesbot gone ? | [03:20] |
| mp_en_viaje: | in other old lulz, http://trilema.com/2014/cunt-size-discussion-this-is-guaranteed-to-be-weird/#footnote_1_53633 | [03:21] |
| mp_en_viaje: | BingoBoingo, should prolly exclude pingbacks and be longer. | [04:22] |
| mp_en_viaje: | anyways ima publish all these bingology trackbkacs seeing how they use the neat select thing, improvement over old ver. | [04:22] |
| feedbot: | http://trilema.com/2019/how-plugrushcom-got-itself-banned-or-heres-what-business-is-not/ << Trilema -- How plugrush.com got itself banned, or Here's what business is not | [04:30] |
| mp_en_viaje: | ahahaha what the everloving fuck! bingo@patreon ?! | [05:21] |
| lobbes: | mp_en_viaje: re: lobbesbot. The heathen VPS it is hosted on is migrating their servers. Hopefully will be back online in 24 hours (I didn't want 100% of my stuff on Pizarro potential central point of failure and all) | [08:41] |
| lobbes: | though I must say, Pizarro uptime has proven to be far superior than any of the heathen options thus far | [08:42] |
| * lobbes | bbl $mines | [08:42] |
| feedbot: | http://ave1.org/2019/lisp-why-step-5/ << ave1 -- Lisp, Why?, step #5 | [08:54] |
| mp_en_viaje: | aok | [09:02] |
| ave1: | I also have to work on my attention span for writing, I'm getting impatient half-way through. | [09:29] |
| mp_en_viaje: | ave1, it's better to adjust article length to your span, and let it work itself gradually. | [10:22] |
| mp_en_viaje: | early trilema articles were short then got longer and more involved over time | [10:22] |
| mp_en_viaje: | lol in a concerted effort to not make mistakes, shrysr 's description of his understanding of the wot thing became significantly vague-r. and of course mistakes still make it in, eg "This rating represents what that person means to you in whatever way you like." is specifically untrue. the number you associated with a rating represens your guess at the likelihood that you will be able to answer a question about that party asked b | [10:54] |
| mp_en_viaje: | y someone who has rated you. | [10:54] |
| mp_en_viaje: | this is why the unknowns problem is an absolute bar to a high rating -- if people keep asking me questions about X that i can't answer, ima eventually drop their rating. | [10:56] |
| a111: | Logged on 2019-07-28 23:01 mp_en_viaje: as per http://btcbase.org/log/2018-05-01#1806991 tradition i don't even have enough information to distinguish between the case where "phf bleeding to death in a minsk ditch" "phf in love forgot all about world" "phf kidnapped by unreported alien invasion" or literally any other alternative. nfi how to approach it, either, tried everything i could think of. | [10:56] |
| mp_en_viaje: | really there's no way to understand the wot outside of the general theory of the field it resolves, oracles and sybils and all that. | [10:56] |
| feedbot: | http://thetarpit.org/posts/y06/098-hunchentoot-iv.html << The Tar Pit -- Hunchentoot: acceptor code review | [11:32] |
| asciilifeform: | spyked: can pleeeez haz comments on your www ? ( at the risk of repeating mp_en_viaje's , srsly, 'no comment box' is quite discouraging in re reading) | [11:38] |
| a111: | Logged on 2019-07-26 18:53 mp_en_viaje: im guessing for this one time http://p.bvulpes.com/pastes/fn1VH/?raw=true will have to be it but for the love of christ, what are you doing to me here ? am i going to simply ignore your articles because i know for a fact i'm not interestreded in reading something i can't comment on and you're forcing on me the dilemma of either not commenting at all or else losing it in pastes ? this won't do, if i use an hour to read a post i | [11:38] |
| mp_en_viaje: | he did say he'll put them in manually. | [11:38] |
| asciilifeform: | tru | [11:39] |
| asciilifeform: | spyked: imho your 'hunchentoot' vivisection illustrates important point : just how much of the complexity of that thing is on acct of idjit tcpism's shit abstractions, i.e. the lengths to which it goes to pretend that the machines aint exchanging short packets in quasi-reliable ordering | [11:40] |
| asciilifeform: | 'acceptors', 'persistent connections', various streamisms, 'listeners', and other 'i can't believe it's not serialport!111' horros | [11:41] |
| asciilifeform: | *horrors | [11:41] |
| asciilifeform: | for yrs nao, asciilifeform thought, 'why the everliving fuck not serve page as a set of luby packets' | [11:42] |
| asciilifeform: | then -- 'magically' -- no moar 'acceptors', 'streams', 'listeners', 'chunkings'... | [11:42] |
| spyked: | asciilifeform, sorry for the annoyance. will certainly do, but the effort to add comments is non-trivial. I'ma try to add structured commenting (box + comments section for each post) in a few weeks from now, but it'll still be a manually operated thing on my side for a while. | [11:44] |
| asciilifeform: | on top of this : could just as easily serve a page from cluster of boxes instead of merely 1 (there's nothing preventing the slices from being generated wherever you want) | [11:44] |
| spyked: | agreed re. tcpism, the "persistent connection" abstraction is entirely unfit for this kind of thing. | [11:45] |
| asciilifeform: | spyked: imho put link to this thread, is even better than pasting the 'comment' | [11:45] |
| asciilifeform: | tcp was a 'gift' of profound retardation that 'keeps on giving', even to moar obvious extent than e.g. unix. it is single-handedly responsible for ~100% of the backbreaking complexicrud of apache, ssh, ftp, etc | [11:48] |
| asciilifeform: | the net aint a serial port!! it dun behave like a serial port! and the spackle dun do any good, it cracks and peels when you so much as blow on it | [11:49] |
| a111: | Logged on 2018-10-25 19:10 asciilifeform: when you add compatibility spackle, serious reader is not saved from reading the thing you spackled over -- on the contrary nao he has to read the ~original~ rubbish ~plus~ your spackle, however much it weighs. | [11:49] |
| a111: | Logged on 2019-02-12 23:49 asciilifeform: mircea_popescu: thinking about it -- 'zxc' strikes me as a classic case of http://btcbase.org/log/2018-10-25#1866191 and impedence mismatch generally. it was clearly written as attempt to 'deterministic scheduler on ??? iron/os', but fails, cuz you can't actually spackle away impedence mismatch b/w the underlying platform and the proggy | [11:49] |
| asciilifeform: | ever wonder why heathens still fascinated, like chukchas with radio found in taiga, with 'bittorrent' ? it's because warez goes at ~line rate~ over 'bittorrent'. and at maybe 2/3 line rate on http on a good weather day. why? cuz bt , despite authored by idiot, ~let go of tcpism~ ! | [11:53] |
| asciilifeform: | as if the ludicrous cpu & bw waste of tcp weren't enuff, it also conveniently groups (with said grouping being entirely plaintext) 'sessions' for hitler to moar conveniently store & read. | [11:56] |
| asciilifeform: | will reproduce bit of spyked's text for the log : | [12:01] |
| asciilifeform: | 'Now, as if this wasn't enough, TCP also has a (transport layer) segment size, which must fit into a so-called "Maximum Segment Size" (MSS), which must be smaller than the MTU, because we also need to fit lower-layer headers and all that. Otherwise TCP isn't concerned too much with this, but misconfiguration can cause problems with congestion windows and whatnot, and we sure as hell don't want this shit to blow up. Finally, as if the | [12:01] |
| asciilifeform: | fuckers who designed the L3 shit and the ones who specced the L4 shit didn't add enough, here come the L7 idiots who, not being satisfied with a "file transfer protocol" decide to "support" file transfers over HTTP and since files may be as large as, say, 1TB, then yes, splitting them into small chunks is very much preferable to sending the whole thing right away.' | [12:01] |
| asciilifeform: | ^ i.e. there are at least ~4~ successive impedance-mismatched layers of liquishit , if you count ~server~ (e.g. hunchentoot) . ~5~ if you count reader's browser ! | [12:02] |
| asciilifeform: | the 'session' abstraction aint even cardboard , it is toilet paper. yes, i get it, ftp or irc box might want to represent a user as having a 'session' that might time out etc. but why give 9000 flaky (or malicious) routers between the user & server the ability to close the session whenever ~they~ feel like it ? | [12:10] |
| BingoBoingo: | http://btcbase.org/log/2019-08-01#1925907 << I noticed the blog was missing incoming some incoming trackback on older posts, so I poked the DB a bit. | [12:28] |
| a111: | Logged on 2019-08-01 07:00 mp_en_viaje: btw, i got like 60 pingbacks from you, that are all dupes. i mean... http://trilema.com/2013/ripple-the-definitive-discussion/#comment-95245 exists, but now theres also one from http://bingology.net/2013/09/26/anti-bitcoin-bitcoin-apps-part-3-gliph-in-particular/?b=Rippl&e=#select | [12:28] |
| asciilifeform: | http://btcbase.org/log/2019-08-01#1925914 << prolly he subscribed to somebody's pay www ? i defo did at 1 pt ( orlol's ) | [13:14] |
| a111: | Logged on 2019-08-01 09:21 mp_en_viaje: ahahaha what the everloving fuck! bingo@patreon ?! | [13:14] |
| BingoBoingo: | asciilifeform: Went fising for derps | [13:15] |
| asciilifeform: | BingoBoingo: caught any ? | [13:15] |
| mp_en_viaje: | BingoBoingo, asciilifeform somehow patreon sent unsolicited email to the email address i published earlier today | [13:15] |
| mp_en_viaje: | i still suispect some kind of ungodly manipulation, because no mailinglist was confirmed or anything like that. | [13:16] |
| asciilifeform: | mp_en_viaje: they send spam like it's 1999 lol | [13:16] |
| mp_en_viaje: | and they know to send it from bingo@patreon ? | [13:16] |
| asciilifeform: | mp_en_viaje: also their pw reset mechanism is broken, i've been trying to log in & cancel acct for 3+ yrs nao (erry 6mo or so) and been to their india-powered 'support line' even. no dice. | [13:17] |
| mp_en_viaje: | in other sad lulz : protonmail.com too pantsuit to... show you the god damned headers. | [13:17] |
| mp_en_viaje: | imagine that wonder of "security" | [13:17] |
| asciilifeform: | what's 'proton' ? disposable spamgourmet thing ? | [13:17] |
| mp_en_viaje: | wanna-be usgistic "encrypted emaik" | [13:17] |
| asciilifeform: | lol, does it come with acct on 'keybase' !? | [13:18] |
| mp_en_viaje: | 2048 bit something, nfi | [13:18] |
| mp_en_viaje: | prolly | [13:18] |
| * asciilifeform | of the 'get the cheapest astrologist' school of thought , on those occasions when must use email | [13:19] |
| mp_en_viaje: | i dun think this costs anything | [13:20] |
| asciilifeform: | if it's 1 of those lulzy 'faux crypto via js' things, costs having-to-login-from-js-browser neh. | [13:20] |
| mp_en_viaje: | shrysr, https://s.ragavan.co/2019/07/failed-to-implement-the-line-selection-to-url-hack/?b=Summary&e=estimate#select << works fine ? | [13:22] |
| mp_en_viaje: | !!up shrysr | [13:22] |
| deedbot: | shrysr voiced for 30 minutes. | [13:22] |
| mp_en_viaje: | this might be the first time i actually get to say to engineer that reported complete failure "oh, actually, it works ?!" | [13:24] |
| mp_en_viaje: | usually it's other way around | [13:24] |
| BingoBoingo: | <asciilifeform> BingoBoingo: caught any ? << Caught a deep impression that US, EE, and SA poverteneur goals are converging to the same 400 USD/month | [13:24] |
| asciilifeform: | BingoBoingo: what does this mean , for beggar to have 'goal' ? maybe i'm thick, but i thought 'goal' was to fill the hat with as many coins as possible erry day ? | [13:26] |
| asciilifeform: | ( what does beggar do if 'not meet goal' ?? on street corner, he could walk to new corner. but what's the 'patreon' equiv ?? ) | [13:26] |
| shrysr: | mp_en_viaje: works fine ?? | [13:27] |
| mp_en_viaje: | yes ? | [13:27] |
| mp_en_viaje: | asciilifeform, move on to being rapper ? | [13:28] |
| shrysr: | mp_en_viaje: I implemented the 2nd article's directions - just tried... not working on my browser | [13:28] |
| BingoBoingo: | <asciilifeform> ( what does beggar do if 'not meet goal' ?? on street corner, he could walk to new corner. but what's the 'patreon' equiv ?? ) << Actual pichis pointedly can't walk to any other corner as they wish because bum fights | [13:28] |
| mp_en_viaje: | note : this guess is bolstered by sampling conversation with a lot of their "girlfriends" | [13:28] |
| mp_en_viaje: | shrysr, must be the browser, because it works as expected here. | [13:28] |
| BingoBoingo: | shrysr: You select thing works from here too | [13:29] |
| mp_en_viaje: | http://archive.is/wjGRL << archive also sees it. | [13:29] |
| asciilifeform: | mp_en_viaje: i thought progression were more usually e.g. x -> y -> rapper -> p -> q -> beggar rather than x -> beggar -> y | [13:29] |
| mp_en_viaje: | asciilifeform, you familiar with qm concepts of proba bility cloud yes ? here it's probability clown : entrepreneur, student, rapper, designer, etc | [13:29] |
| asciilifeform: | shrysr: indeed your select display seems to work | [13:29] |
| shrysr: | HOLY SHIT | [13:30] |
| mp_en_viaje: | keks | [13:30] |
| asciilifeform: | mp_en_viaje: lol i have'em moar 'classically' modeled as simply 'beggar' energy level | [13:30] |
| mp_en_viaje: | not adequate! | [13:30] |
| asciilifeform: | evidently | [13:30] |
| shrysr: | mp_en_viaje: i thought the 2nd solution browser independent? I'm using the firefox dev edition | [13:32] |
| * asciilifeform | pictures 'hybridization orbital' for rapper-designer etc | [13:32] |
| mp_en_viaje: | shrysr, nfi why it doesn't work on your machine. indeed the solution should be browser independent. maybe they broke the spec ? | [13:32] |
| mp_en_viaje: | asciilifeform, foreals. | [13:33] |
| mp_en_viaje: | this is factual, and predictively-productive. | [13:33] |
| asciilifeform: | 'Note taken on <span class="timestamp-wrapper"><span class="timestamp">[2019-07-31 Wed 09:17] </span></span> <br /> <span style="background-color:#d3d3d3" id="select">Summary: By my estimate</span>, I have spent 6-8' << oughta display anywhere | [13:34] |
| feedbot: | http://qntra.net/2019/08/qntra-s-qntr-july-2019-report/ << Qntra -- Qntra (S.QNTR) July 2019 Report | [13:34] |
| asciilifeform: | 'lynx' does report 'bad html' tho | [13:35] |
| asciilifeform: | (but naturally dun say ~where~...) | [13:35] |
| shrysr: | mp_en_viaje: just tried on a 'fresh' chrome installation.. still don't see it. | [13:35] |
| mp_en_viaje: | wtf. | [13:35] |
| * asciilifeform | tried on several chromisms, all seem to display | [13:36] |
| asciilifeform: | shrysr: i suspect there's an unclosed tag somewhere | [13:36] |
| asciilifeform: | most of the extant browsers do the idjit 'postel's law' thing where they 'fix' | [13:37] |
| a111: | Logged on 2018-02-02 16:23 asciilifeform: the 'postel's law' nonsense, of silently forgiving people who send liquishit at the dusty disused corners of the protocol, enabling there to even ~be~ such a thing as dusty corners in a protocol!, MUST die. | [13:37] |
| asciilifeform: | evidently not all | [13:37] |
| feedbot: | http://trilema.com/2019/kiev-the-continuation/ << Trilema -- Kiev, the continuation. | [13:37] |
| shrysr: | asciilifeform: ok, will check and revert. but damnnnnnn its working somewhere..rofl. Its such a cool thing and I don't know why its not standard. | [13:37] |
| mp_en_viaje: | shrysr, the current theory seems to be indeed his : your page is subtly broken somewhere else, which makes this not work on some browsers but not others. put it through validators see if you can find the unclosed tag or we/ | [13:38] |
| shrysr: | ok | [13:38] |
| asciilifeform: | shrysr: mp_en_viaje's orig item worx 100% errywhere (that i've tried) | [13:38] |
| mp_en_viaje: | shrysr, indeed, wanna try the select on my page on yoru browsers ? | [13:38] |
| asciilifeform: | epic win, btw, the server-end highlighter. i'ma put it in my www as soon as have a free finger or two | [13:39] |
| mp_en_viaje: | if it works there it's almost certain such a subtle error in your theme, as an uncliosed div or span or such | [13:39] |
| shrysr: | mp_en_viaje: yes selection on your pages work, and so does younghands.club, .. seen it before and just rechecked. | [13:40] |
| mp_en_viaje: | right. validate your theme and see. | [13:40] |
| mp_en_viaje: | (fwiw, trilema spits out deliberately invalid html, also) | [13:41] |
| mp_en_viaje: | in other scandal, by the time i hit "[wafs] wake-acceptor-for-shutdown" in spyked 's story i'm so fucking pissed off i can't even continue reading. | [13:43] |
| mp_en_viaje: | why the fuck is this hunchenback even written in lisp ? it's pure python, why not just write it in python and be happy. | [13:43] |
| asciilifeform: | mp_en_viaje: i was only able to eat w/out choking because already, decade+ ago, had read 'hunchentoot' an' barfed | [13:43] |
| mp_en_viaje: | this is not a lisp program. | [13:44] |
| asciilifeform: | point is , tho, that it is barfalicious ~because tcp~, not because author as such was tard | [13:44] |
| asciilifeform: | you can't actually write a tcpistic http serv thing that doesn't end up looking exactly like this, or worse. | [13:44] |
| mp_en_viaje: | it's the exact equivalent of enunciating english words with an o at the end to speako el mexicano, understando ? | [13:44] |
| asciilifeform: | mp_en_viaje: imho described upstack 100% covers it. | [13:47] |
| a111: | Logged on 2019-08-01 15:40 asciilifeform: spyked: imho your 'hunchentoot' vivisection illustrates important point : just how much of the complexity of that thing is on acct of idjit tcpism's shit abstractions, i.e. the lengths to which it goes to pretend that the machines aint exchanging short packets in quasi-reliable ordering | [13:47] |
| asciilifeform: | mp_en_viaje: at one time in '17 asciilifeform tried hand at writing basic ada www server. ended up burning it all. because ended up looking quite like 'hunchentoot', and quite evidently 'water took the shape of the bottle', i.e. inescapably | [14:06] |
| mp_en_viaje: | ok, but it's stll not fuckin glisp in any meaningful sense. | [14:07] |
| mp_en_viaje: | i don't specifically care re the culprint but i do not see the wisdom of having a lisp server if it looks like that. for one thing, if you just make it honest c more people can be found to debug it. | [14:07] |
| asciilifeform: | imho if stuck with ugly piece of shit, would still rather have one w/out the nulltermstring, buf overrun, offbyone, etc. bugola. but i see mp_en_viaje's pt | [14:09] |
| mp_en_viaje: | i also do not believe that going about in ox-drawn carts with "Mercedesuzuki" spray-painted on the sides "will aid people to migrate to cars later" or anything | [14:09] |
| mp_en_viaje: | asciilifeform, that might be an argument for ada. but not for lisp. lisp comes with interpreter costs etc. | [14:10] |
| asciilifeform: | mp_en_viaje: cl (aside from egregiously retarded incarnations, e.g. gnu's) aint interpreted, lol | [14:10] |
| mp_en_viaje: | i thought this required gnu cl | [14:11] |
| asciilifeform: | penalty (given similar algo) is approx same as ada's | [14:11] |
| asciilifeform: | mp_en_viaje: hunchentoot is known to run on e.g. sbcl, ccl , where compiled. | [14:11] |
| mp_en_viaje: | ah | [14:11] |
| mp_en_viaje: | anyway, i'm not proposing any hangings today but we also can't just completely ignore this ridiculousness wtf. | [14:12] |
| asciilifeform: | in asciilifeform's judgement, the retardation is pulled in ~by the protocol per se~ . but folx are welcome to try an' prove wrong. | [14:12] |
| mp_en_viaje: | irrespective of how it gets in -- the fact remains, it's STILL not lisp, even if "written in lisp". cuz it's "written in lisp*" where * = as if it were not lisp | [14:13] |
| asciilifeform: | 'fortran in lisp'(tm) | [14:14] |
| mp_en_viaje: | ikr ?! | [14:15] |
| mp_en_viaje: | http://btcbase.org/log/2019-08-01#1925939 << this is incidentally a very good point i would much regret being lost. webpages wouldn't suffer from this "coinverges -- eventually" behaviour | [14:15] |
| a111: | Logged on 2019-08-01 15:44 asciilifeform: on top of this : could just as easily serve a page from cluster of boxes instead of merely 1 (there's nothing preventing the slices from being generated wherever you want) | [14:15] |
| mp_en_viaje: | and yes, suddenly multi-server becomes free. | [14:15] |
| asciilifeform: | and ddosism evaporates. | [14:15] |
| mp_en_viaje: | besides, the mechanism splendidly demonstrared in torrents, not like this is arcana toch | [14:16] |
| mp_en_viaje: | tech* | [14:16] |
| mp_en_viaje: | yup. | [14:16] |
| asciilifeform: | re torrent -- noted, btw, upstack | [14:16] |
| a111: | Logged on 2019-08-01 15:53 asciilifeform: ever wonder why heathens still fascinated, like chukchas with radio found in taiga, with 'bittorrent' ? it's because warez goes at ~line rate~ over 'bittorrent'. and at maybe 2/3 line rate on http on a good weather day. why? cuz bt , despite authored by idiot, ~let go of tcpism~ ! | [14:16] |
| mp_en_viaje: | it is very evidently and most eminently the only rught thing. | [14:16] |
| asciilifeform: | mp_en_viaje: btw this is another application where box with FG wins -- generating fast-converging luby frags | [14:18] |
| asciilifeform: | ( even if you have to 'stretch' the FG w/ prngism, still 9000x moar convergence than with bare hands ) | [14:18] |
| mp_en_viaje: | not even sure must be lubby necessarily but anyways | [14:19] |
| asciilifeform: | mp_en_viaje: there are actually coupla dozen (that asciilifeform knows of) schemes similar in scope to luby's -- i picked his simply cuz a) works b) minimal complexity | [14:19] |
| mp_en_viaje: | nor am i against it or anything. | [14:20] |
| mp_en_viaje: | but the stance seems tenable that if we're gonna go to all the trouble to make and maintain lisp webserver, might as well make a non-fucked one and make new browsers for it | [14:21] |
| asciilifeform: | it is far from proven that it could not be substantially improved on. but afaik a) only along the axis of bw economy b) at substantial expense in re moving parts. | [14:21] |
| asciilifeform: | ( this in re luby's algo ) | [14:21] |
| mp_en_viaje: | and if not wanna actually fuck, then get out of the night club, go home, have a tea | [14:21] |
| mp_en_viaje: | which rapidly collapses "lisp webserver" into gossipd and all that. | [14:21] |
| asciilifeform: | strictly speaking , udpistic page server doesn't even require gossipism. but ideally yes. | [14:22] |
| asciilifeform: | ( why would ~not~ want ? conceivably, cuz rsa is expensive. at least until we have e.g. that 8192bit mips iron, or similar ) | [14:23] |
| mp_en_viaje: | can start with a non-cyphered poc antyway | [14:25] |
| asciilifeform: | an' if 'sane server', and 'fuck or go home and tea', may as well then also serve up sexpr instead of the html soup. | [14:28] |
| mp_en_viaje: | yes. | [14:30] |
| mp_en_viaje: | why the fuck would lisp webserver serve ANYTHING ELSE | [14:30] |
| mp_en_viaje: | it makes no fuckin gsense at no node in the whole fractal tree of stupid. | [14:30] |
| asciilifeform: | the only conceivable reason why httpism lived (for 3!! fucking decades) is cowardice. 'oh noez, couldn't tell reader to install sane browser, MUST compat with internet-exploder' etc | [14:32] |
| mp_en_viaje: | but now ~that there is structure of authority~... eminently CAN tell. | [14:32] |
| mp_en_viaje: | especially seeing how nobody is forced or required to fucking use it not for a while anyways. can always fall back on present c-ism if would rather. | [14:33] |
| mp_en_viaje: | this is basically the discussion here, properly identify the quantified states. | [14:33] |
| asciilifeform: | reason why 3 decade of 'apache' is same as why erryone (incl. microshit) is using that SAME tcp stack from berkeley '80s. cuz protocol was deliberately made so braindamaged, with literally 10,000+ moving parts, that ~impossible to correctly reimplement if demanding compat with 'everyone' | [14:35] |
| asciilifeform: | the correct end of the funnel to plug, is to burn the protocol. | [14:35] |
| asciilifeform: | (same thing we're doing to gpg's rfc2440 etc) | [14:35] |
| asciilifeform: | there's a long queue of 'idjit standards that Must Die if anyffin sane is to be possible'. on other side of the tower, e.g., x86. | [14:39] |
| asciilifeform: | 'из говна пулю не сделаешь'(tm)(r) | [14:41] |
| asciilifeform: | prolly this is where asciilifeform oughta admit, that in his notebook he has (what thinks is) a reasonable protocol for this. it however needs fast keccak. | [15:08] |
| asciilifeform: | ( cleanly handles the multi-box scenario, too. ) | [15:08] |
| mp_en_viaje: | http://btcbase.org/log/2019-08-01#1925973 << i dunno that non-js webmail thing exists. | [15:21] |
| a111: | Logged on 2019-08-01 17:20 asciilifeform: if it's 1 of those lulzy 'faux crypto via js' things, costs having-to-login-from-js-browser neh. | [15:21] |
| asciilifeform: | mp_en_viaje: 'mailinator', 'gmx', etc spamtraps still afaik work | [15:47] |
| * mp_en_viaje | is admittedly not keeping too close an eye | [15:52] |
| dorion: | I have a trb node pressed to asciilifeform_aggressive_pushgetblocks.vpatch plus a local modification to add a new rpc. This node was was fully synced for a couple days, but has failed to verify block 588012. | [17:01] |
| dorion: | http://p.bvulpes.com/pastes/gQ05f/?raw=true << Here is debug.log snippet since receiving 588011. ~300 lines in it fails on 588012. | [17:02] |
| dorion: | The remainder of that file is the remainder of the hour in which it attemps several reorgs. | [17:02] |
| mp_en_viaje: | is it actyually block 588012 hash 0000000000000000000ba68c82d9b620cf028f0642c833a5eda92dbf68d5a3fb ? or is it the next, hafsize one, hash 0000000000000000001498ec3c9796a44b53b8b70186920d15a5e34afcaaa719 ? | [17:18] |
| dorion: | because the hash is truncated in the log, it only indicates the leading b for 588012. | [17:24] |
| dorion: | Given the truncated hashes, I pressed to asciilifeform_whogaveblox.vpatch (which includes mod6_excise_hash_truncation.vpatch), stopped the node and restarted with the new binary. | [17:25] |
| dorion: | http://p.bvulpes.com/pastes/qT7ce/?raw=true << Here is first 200 lines from debug.log after the restart. | [17:25] |
| dorion: | http://p.bvulpes.com/pastes/kpTWI/?raw=true << Here is the snippet starting at first reorg attempt in that run. | [17:26] |
| dorion: | when I grep 0000000000000000000ba68c82d9b620cf028f0642c833a5eda92dbf68d5a3fb debug.log it reports to have | [17:28] |
| feedbot: | http://trilema.com/2019/thelastpsychiatristcom-are-there-really-so-many-people-with-such-troubles-in-your-country-to-make-such-medicine-such-an-important-matter-adnotated/ << Trilema -- thel....com - "Are there really so many people with such troubles in your country to make such medicine such an important matter?" Adnotated. | [17:32] |
| asciilifeform: | hmm dorion why didja build w/out the de-truncation patch ? | [17:37] |
| asciilifeform: | pretty sure it made it into the flagship vtree | [17:38] |
| asciilifeform: | ( mod6 ? ) | [17:38] |
| asciilifeform: | dorion: '08/01/19 01:11:33 InvalidChainFound: invalid block=0000000000000000000b height=588012 work=2327381792950809691787748424' << somebody's sending invalid blox. happens erryday. | [17:39] |
| asciilifeform: | 0 to do with trb. | [17:39] |
| dorion: | asciilifeform de-truncation is marked experimental on btcbase.org/patches and thebitcoin.foundation/v/patches | [17:42] |
| asciilifeform: | dorion: http://nosuchlabs.com/pub/588012.blk << blk # 588012 from zoolag. | [17:42] |
| dorion: | ty, stopping now and restarting with -caneat | [17:47] |
| asciilifeform: | of erry 20 folx that ask re 'my trb stopped at block B', 19 problem is impatience. | [17:47] |
| asciilifeform: | !Q later tell mod6 is something wedging your conveyor re eating patches ? plz do say. cuz e.g. detruncation is iirc >1y old nao | [17:49] |
| asciilifeform: | grr lobbes bot dead ? | [17:49] |
| * asciilifeform | brb:teatime | [17:49] |
| asciilifeform: | dorion: 'Reorganize() : ConnectBlock failed' is emitted strictly when encountering invalid block. | [18:20] |
| dorion: | after restarting with -caneat, bitcoind eatblock 588012.blk returns: error: {"code": -2, "message":"Safe mode: WARNING: Displayed transactions may not be correct! You may need to upgrade, or other node may need to upgrade." | [18:21] |
| dorion: | it also returns this on getbalance, listtransaction, etc. | [18:21] |
| asciilifeform: | dorion: nao this is interesting. can you dumblock the last 20 or so and tar'em up, post , plz. | [18:22] |
| asciilifeform: | *dumpblock | [18:22] |
| asciilifeform: | seems like this is what happens if one terminates a node on even fork-split boundary. | [18:27] |
| asciilifeform: | dorion: you may have to restart with '-disablesafemode' flag, to resume sync. | [18:28] |
| asciilifeform: | and it may take a while. | [18:28] |
| asciilifeform: | mp_en_viaje et al : ^ pretty nasty , surprised no one has observed this effect before. | [18:29] |
| asciilifeform: | at this pt, seems quite evident that someone is throwing around crafted wedge chains (i.e. mined after-the-fact , with backdated timestamp, going from older block) specifically to wedge syncing folx. | [18:31] |
| asciilifeform: | if mod6 had the detruncation and the 'who-gave' patches in the flagship tree, we could even potentially find out who... | [18:34] |
| asciilifeform: | for ref: 'who-gave' patch. | [18:35] |
| a111: | Logged on 2018-09-29 22:11 asciilifeform: ACHTUNG, panzers!!! http://therealbitcoin.org/ml/btc-dev/2018-September/000312.html << . | [18:35] |
| asciilifeform: | dorion: you will have to show your local modification if you want to be 100% certain wtf yer node is doing. | [18:39] |
| a111: | Logged on 2019-08-01 21:01 dorion: I have a trb node pressed to asciilifeform_aggressive_pushgetblocks.vpatch plus a local modification to add a new rpc. This node was was fully synced for a couple days, but has failed to verify block 588012. | [18:39] |
| asciilifeform: | and hey jurov, can i persuade you to update http://btc.yt/lxr/satoshi/source/ to contain the latest flagship tree plz ? | [18:42] |
| asciilifeform: | ( as it is, 99% of threads are served by the older snapshot, cuz they concern very basic mechanisms -- but the line #s are liable to be off ) | [18:42] |
| lobbes: | http://btcbase.org/log/2019-08-01#1926113 << hopefully will return soon (TM) >> http://btcbase.org/log/2019-08-01#1925915 | [18:48] |
| a111: | Logged on 2019-08-01 21:49 asciilifeform: grr lobbes bot dead ? | [18:48] |
| a111: | Logged on 2019-08-01 12:41 lobbes: mp_en_viaje: re: lobbesbot. The heathen VPS it is hosted on is migrating their servers. Hopefully will be back online in 24 hours (I didn't want 100% of my stuff on Pizarro potential central point of failure and all) | [18:48] |
| * asciilifeform | bbl:meat | [18:48] |
| feedbot: | http://qntra.net/2019/08/dnc-loses-2016-hack-related-racketeering-suit/ << Qntra -- DNC Loses 2016 Hack Related Racketeering Suit | [18:49] |
| mod6: | Hey there | [19:17] |
| mod6: | http://btcbase.org/log/2019-08-01#1926112 << These go back to this, I did test those ones when they came in. iirc they did work alright when I tested them. I stopped adding these items to the working vtree (SHA512) when mircea_popescu said, and instead started working towards getting the keccak vtree built & then getting it onto cuntoo. Figured once there & stab | [19:22] |
| a111: | Logged on 2019-08-01 21:49 asciilifeform: !Q later tell mod6 is something wedging your conveyor re eating patches ? plz do say. cuz e.g. detruncation is iirc >1y old nao | [19:22] |
| a111: | Logged on 2019-07-24 00:56 mod6: http://btcbase.org/log/2019-07-19#1923606 << This is a neat-o vpatch 'who gave', but it came in just after the 'NO NEW WORK IN SHA PLOX' so there are a few like this that probably will go into TRB main Vtree once the Lordship reviews/audits the proposed Keccak TRB Vtree perhaps possibly after TRB has a new home OS/environment. | [19:22] |
| mod6: | le, could begin retroactively testing & adding these older submissions into the tree. | [19:22] |
| mod6: | I've been pondering mircea_popescu's reponse to the above link since the statement was made. I'm not sure how I went wrong here, but not adding to the existing SHA512 vtree is what I understood my instructions to be. | [19:24] |
| mod6: | I think my head must be broken, because the stress of making a decision wrong is paralyzing. | [19:25] |
| mod6: | It seems like Mr. Popescu feels the same way. That I should be drummed out. We've known each other (all of us) for quite some time now. And I don't want to be a "problem" or "idjit" or whatever. Mainly, I don't want to force you all to kick me out. | [19:28] |
| mod6: | Or tell me to leave. | [19:28] |
| mod6: | So I should just do this on my own accord. Shall we make some arragements for someone to take over the Foundation? How can we go about this. I want to see TMSR~/The Foundation/Pizzaro succeed. Even if that means that I'm not a part of these any longer. | [19:30] |
| mod6: | This year, I've done what I could with the time I have available, which, indeed, is far less time than I've had in say, '11-'16. I know I haven't produced as much as I would like this year, especially in July. I've had so much secular stuff come up, my head is spinning. But reality is, I barely have enough time to keep up with the logs. | [19:33] |
| mod6: | TMSR~/The Foundation/Pizarro deserve better. | [19:33] |
| mod6: | Heck, for what its worth, I know that there has been some talk about reorganziation of Pizarro's roles/responsibilities since after this latest round, that if I'm causing strife/headaches, I'd even be willing to split my shares between BingoBoingo and asciilifeform, and you guys can continue one. | [19:36] |
| mod6: | s/one/on/ | [19:37] |
| mod6: | But all of this has beaten me down. I've been trying to soldier on this year, being productive, helpful. But it's not working out, is it? | [19:38] |
| mod6: | Like I said earlier this year, I do care about my wot-rating, so I don't want to damage that. Let's discuss/work together to help me move on from these things. | [19:40] |
| mod6: | I've got to stop moving for a minute and eat something, and then write up a basic nothing-burger of a foundation report. I'll be back around in a bit. | [19:41] |
| asciilifeform: | * a111 has quit (Quit: ...) << ! | [20:55] |
| asciilifeform: | ben_vulpes ( or trinque , plox to whisper in his ear ) : phf might be dead, but afaik you aint! where is the genesis of yer www log front end ? why are we down to ONE half-maintained log bot ? does asciilifeform have to drop errything and try an' bake a logger ? why ? | [21:16] |
| asciilifeform: | ftr asciilifeform is sewing a constant-time keccak so that peh can rsa in battlefield. is someone gonna do this in my place, so i can write www log ?? | [21:25] |
| asciilifeform: | and, the other q, is writing log www somehow lethally dangerous work ?! kako wrote -- succumbed to brain fungus. Framedragger -- succumbed. phf -- ditto. ben_vulpes -- ???! | [21:29] |
| asciilifeform: | what the fuck is the common thread there?! | [21:30] |
| mod6: | http://therealbitcoin.org/ml/btc-dev/2019-August/000335.html << Here's The Foundation report for July. | [22:17] |
| mod6: | Ah, jeeze. mircea_popescu isn't here is he. | [22:20] |
| mod6: | !Q later tell mp_en_viaje http://p.bvulpes.com/pastes/OmWqw/?raw=true << Saw the logger died and you were not in-chan. | [22:24] |
Category: Logs
