log☇︎
43400+ entries in 0.345s
asciilifeform: !A .0.0.0.0.0.0.1 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
asciilifeform: !A .0.3.0.0.0.0.1 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
asciilifeform: !A .4.3.0.0.0.0.1 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
asciilifeform: !A .4.3.6.0.0.0.1 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
asciilifeform: !A .4.3.6.0.FF.0.1 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
ben_vulpes: !A .4.3.6.ABCD.FF.0.1 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
asciilifeform: !A .4.3.6.ABCD.FF.0.1 ( ben_vulpes's solution goes here ) Q
asciilifeform: i thought ben_vulpes was speaking of a soln to the branch thing
ben_vulpes: oh sorry sorry, i meant a solution to the ch4 puzzle
ben_vulpes: i haven't bitten off the patch yet, and might not get to it by the time you release ch6, this all takes me a lot longer than phf or lobbes
ben_vulpes: well, gonna reread vpatch for ch04 and then submit with my seal but sure, gimme a sec
ben_vulpes: a solution!
asciilifeform: then the optional else-clause could be preceded by a ~
a111: Logged on 2018-01-03 17:17 asciilifeform: http://btcbase.org/log/2018-01-03#1763202 << i've been thinking of abolishing the artifact where a 0 stays on the stack after the 'else' branch. it'd require only 1 extra state variable ( a WBool )
a111: Logged on 2018-01-03 17:07 phf: using the boolean we execute an if/else branch which either swaps the two numbers and drops the top most '_, or drops the top most without swapping _. the final drop _ is an artifact of conditional implementation that always leaves a value on the stack.
asciilifeform: a { takes a value off the stack and, if it is 0 : ignores further ops until it gets a ~matching~ } , then leaves a 1 on the stack; if it is a 1, proceeds to the next op , and when a closing } is found , leaves a 0 on the stack.
asciilifeform: ( what we have right now, is that we have no 'if-clause' or 'else-clause', physically, they are exactly the same thing, simply happen to be a pair of'em )
asciilifeform: feel free to submit a patch.
asciilifeform: !A .1{[foo]}{[bar]} Q
asciilifeform: !A .1{[foo]}{[bar]}_ Q
ben_vulpes: !A .1{[foo]}{[bar]}
ben_vulpes: !A .1{[foo]}{[bar]}_
asciilifeform: !A .0{[foo]}{[bar]} Q
asciilifeform: !A .0{[foo]}{[bar]}_ Q
ben_vulpes: i am having just a terrible time with the else-clause pushing a zero to the stack
asciilifeform: 'Stay connected, chat from anywhere, and never miss a message.'
ben_vulpes: a modern IRC client that keeps you connected, with none of the baggage
asciilifeform: what makes you think it's a bouncer, ben_vulpes
ben_vulpes: dude The20YearIRCloud the fuck even is the point of a bouncer that's constantly disconnecting
a111: Logged on 2018-01-03 17:17 asciilifeform: http://btcbase.org/log/2018-01-03#1763202 << i've been thinking of abolishing the artifact where a 0 stays on the stack after the 'else' branch. it'd require only 1 extra state variable ( a WBool )
a111: Logged on 2018-01-05 15:40 mod6: I went through each one, looks to be doing the sane thing. I'm probably going to write it up in a little post that can be looked at, as opposed to trying to explain all of that in 3 lines of irc.
mod6: Ok, will look into a better way to handle this. I appreciate your passionate want to make this better.
mod6: So here's what I'll do: I'll revisit this, and try to come up with a unique tempdir. This tempdir is to be used exactly once. Created at run time. Removed at the end of run time. If execution fails or is interrupted, nothing will be done. It'll be left hanging there until the user removes it manually.
mod6: And I've taken a bit of a different direction, perhaps because of 'File::Tempdir' or some nonsense.
asciilifeform: 'A TLV (type-length-value) structure is parsed and copied on to the parent stack frame. Unfortunately, there are missing bounds checks, and a specially crafted certificate can lead to a stack overflow...' etc
asciilifeform: '... stack-based overflow in the function EkCheckCurrentCert. This function is called from TPM2_CreatePrimary with user controlled data - a DER encoded [6] endorsement key (EK) certificate stored in the NV storage....' ☟︎
asciilifeform: !A .1.0*#
mircea_popescu: why should he give a shit in either case.
asciilifeform: fell over like a bowling pin after 'shown instrments'
a111: Logged on 2018-01-05 15:40 mod6: I went through each one, looks to be doing the sane thing. I'm probably going to write it up in a little post that can be looked at, as opposed to trying to explain all of that in 3 lines of irc.
mod6: lemme break off here for a minute, i'll keep digging up the logs to prove we talked this over.
mod6: it sounds like my idea of "have something of a corpus to look at after failure" isn't as handy as simply just throwing it out.
asciilifeform: if you have a handle to it, it dun get zapped
trinque: I don't think there's ever a case where , yeap
mod6: maybe mktmpdir is sound for that. however, i remember discussing that before as well..and one fear that i had is that if you use mktmpdir, then you have a /tmp/23429adfsew32 dir.
mod6: anyway, if you see a .gnupgtmp, something failed. either the software failed, or the user interrupted the thing. either way, the responsibility has been on the user to determine if he should delete ~/.gnupgtmp or not.
asciilifeform: mod6: imho a good debugism would be a flag that forces the printing to stderr of all external proggy (gpg, gnupatch) invocations , and their args
a111: Logged on 2018-01-05 13:34 asciilifeform: http://btcbase.org/log/2018-01-05#1764882 << i'm quite tempted to give the archive another combing and make a sequel to my http://www.loper-os.org/?p=165 item
mod6: i shouldn't say a lot. from time to time, one of alf's previous key ones would creep into ones flow or whatever, and you may want to check for yourself weather it verifies or not. or what gnupg might have been up to while executing v.
mod6: and if it did fail, then perhaps one can go and look at what went on -- at the time, there were a lot of seals that didn't verify for instance.
mod6: its basically a failure state -- .gnupgtmp should only be around if something FAILED.
asciilifeform: soo analogously 'plaintext' would be 'the integers'(tm)(r) whereas asciilifeform's conception would then be the finite-bitness integers one actually gets to use on a comp
asciilifeform: !A .BE7EA8B353CF33FA1226E6F87F97CE980353879CA9F00107C2DE4E123ECBE000.7D2AF9FAA2CD4F3CCFE8489B9BE1FE5F3A600D4E1E72A7C0041F0B793848FB2F.FA55F3F5459A9E799FD0913737C3FCBE74C01A9C3CE54F80083E16F27091F65F X #
asciilifeform: ok that'd be a platonic plaintextitude, lol, not a physical item.
mircea_popescu: here, from random article : Sorry, furfies looking for group, I guess I fucked this one up for you ((But had you NOT complained about it -- who knows, maybe you'd still have PMs available ?)).\n\nPS. Today as in <A href=http://trilema.com/2014/askfm-laid-bare-or-whats-half-a-million-uniques-to-you/>2014</a>,
mircea_popescu: formally : a stackless, hapless grammar incapable of recursion operating upon a certain finite symbol list.
asciilifeform: whereas it's just an array of asciiola and a few control chars (e.g. lf)
mircea_popescu: asciilifeform neh! i have a magic box, into which i pour the transcendent substance that makes trilema. it comes out as ascii yes, but how is it plain.
asciilifeform: trinque: i'd bet d00d has spells of sobriety, he has afaik already outlived the expected life of a serious meth aficionado ☟︎
trinque: wiser folks hitting you on the head is a kindness.
jhvh1: shinohai: Error: "step" is not a valid command.
asciilifeform: maybe d00d sobers up for a day and does a job !
asciilifeform: do you now have a comp and able to work ?
gabriel_laddel: I never got a chance bc fighting all the idiots in CA myself. Same with archiver.Got banned before was able to host in house someone OK'd me for.
asciilifeform: ( because asciilifeform actually did a very similar experiment as a student, in early 2000s )
gabriel_laddel: training a NN on FG output to see if it trains faster so I can sell them ☟︎
asciilifeform: gabriel_laddel: here's a shot : take this http://btcbase.org/log/2017-12-29#1760563 needleman-wunsch, and turn it into a standalone ( use sbcl's save-lisp-and-die knob, say ) difftron util. come up with own format. ☝︎
trinque: where's that, or was that just a paste one day when he needed a self-esteem boost
asciilifeform: at 25 asciilifeform unsuccessfully peddled an industrial automation linux+sbcl+proggy-in-a-crate actually quite reminiscent of gabriel_laddel's thing
trinque: who gives a shit. I made mine because it was trivial and I didn't want to hear about it anymore
ben_vulpes: mod6: it's not a personal attack, i disagree that i agreed that v.pl was doing the Right Thing in leaving ~/.gnupgtmp hanging around
asciilifeform: trinque: iirc he did have a standalone gentoo-cooker neh
asciilifeform: trinque: barf all you like, the d00d nearly made a working cuntoo
trinque: gabriel_laddel: honestly why should anyone give a fuck to improve you.
ben_vulpes: mod6: make a disposable tempdir like stans original and my port. i don't know whence this 'agree', stan's original was clear enough.
a111: Logged on 2015-12-25 23:10 asciilifeform: because, again, the whole 'plain text' jwzism and the attendant retardation. somehow 'lines' are a thing.
mod6: i know, i haven't had a chance to look yet.
mod6: <+asciilifeform> second , as in the case discussed in the thread, if a run aborts, it creates a mine for next run to step on. << try to realize that this is on-purpose. im certain that we've had this discussion before and what exists is the outcome of that discussion.
mod6: <+asciilifeform> no good. first of all suppose there are 2 concurrent runs of the vtron ( say this is a cuntoo pressing itself ) << yeah, concurrent runs of my vtron are a no-go.
gabriel_laddel: and can I call M a NOT-LISPM?
mircea_popescu: it's actually SO BAD that people go re-implement the same damned X thing for the 90th time as a substitute of commentary ; and nobody looking understands wtf that is.
mircea_popescu: there's a reason your father+grandfather haven't amounted to as much of a fart as a workable os.
asciilifeform: and anyone who dunlike it , can jump in a lake.
mircea_popescu: this is a sad state of affairs, as it limits v utility drastically ; neverthless -- commentary will be ok, long predated either v or code. code is more fragile.
ben_vulpes: want to corroborate what appear to be facts before plowing down a possibly retarded path though
asciilifeform: ( whynot, is not a bad question, it reduces to the absence of a solution to the tednelson problem -- how to point into a structure unambiguously, other than by line # ) ☟︎
mircea_popescu: "we are incapable to reflow and here's a magic number instead" differentiates monkey from man
a111: Logged on 2018-01-05 09:56 diana_coman: which is perfectly fine with me for code; it's still grating for comments and I'm not sure how this will resolve, it sort of pushes comments out of code (to a place where one can read them as text not as code-which-they-are-not)
mircea_popescu: http://btcbase.org/log/2018-01-05#1764893 << yeah tis a problem ;/ ☝︎
asciilifeform: so ben_vulpes do you see a jump ?
ben_vulpes: i only started thinking about compute because of bitcoin, and shortly after i started thinking about it in earnest (like maybe a month, six weeks something like that) you showed up in #b-a and /even at that point/ were talking about eg trinary circuits and computing fabric
ben_vulpes: it all strikes me as so very silly on the surface but i have a weird lens of not having thought about any of the related shit until ~2013 and even then only through republican eyes
asciilifeform: on the other hand, pipeline idea per se was a mistake; same kind of failure to invent dataflowism as dma
asciilifeform: ( on vliw, there was a pipeline, but proggy was expected to fill it 'by hand' . a kind of 'stick shift'. if a sub-instr stepped on another's toes, it was a eggog, like div0 is on x86 , abort . )
asciilifeform: bbbut noooo, gotta reorder, because Only A Terorrist Would expect microshit to write sane compiler... ☟︎
asciilifeform: a la vliw.
asciilifeform: it's a gnu coreutil. so theoretically yes
asciilifeform: ( make a string out of /dev/random crapola + current epoch time, say ) ☟︎
asciilifeform: you can fix the second by erasing at the beginning of a run. but not the first.
asciilifeform: second , as in the case discussed in the thread, if a run aborts, it creates a mine for next run to step on.