log☇︎
57600+ entries in 0.014s
asciilifeform: !A .0.0.0.0.0.0.0 ``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_``>{_}{'_}_ Q
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
asciilifeform: http://btcbase.org/patches/ffa_ch5_egypt/tree/ffa/ffacalc/ffa_calc.adb#L232 << for reference
asciilifeform: recall how constants work to begin with
asciilifeform: why would it matter
asciilifeform: ... oughta output ABCD etc
asciilifeform: !A .4.3.6.ABCD.FF.0.1 ( ben_vulpes's solution goes here ) Q
asciilifeform: !!pehbot .4.3.6.ABCD.FF.0.1 ( ben_vulpes's solution goes here ) Q
asciilifeform: or rather, feed to pehbot
asciilifeform: so let's hear ben_vulpes's answ
asciilifeform: it dun use no fancy book-larnin'
asciilifeform: dunno, this item is in principle accessible to the n00b
asciilifeform: i thought ben_vulpes was speaking of a soln to the branch thing
asciilifeform: aaaaaaaa lok
asciilifeform: point being, if you patch on an existing ffa_calc, it'll have to be reground
asciilifeform: consider describing it here then
asciilifeform: or it won't go into ch6 (or anywhere)
asciilifeform: patch on top of ch5 plox ☟︎
asciilifeform: post?
asciilifeform: hm?
asciilifeform: so {[foo]}{[bar]} would then instead look like {[foo]}~{[bar]}_ grrrrrr ☟︎
asciilifeform: phf, ben_vulpes , mircea_popescu , et al ^
asciilifeform: otherwise , if we do not want the else-clause, we drop _ it.
asciilifeform: and trigger on the negation of that selfsame selector.
asciilifeform: then the optional else-clause could be preceded by a ~
asciilifeform: if { were to LEAVE THE SELECTOR on the stack , instead of eating it
asciilifeform: aaaactually i can think of 1 way :
asciilifeform: grrrr http://btcbase.org/log/2018-01-03#1763210 i mean. ☝︎
asciilifeform: and btw i gotta take back http://btcbase.org/log/2018-01-03#1763202 -- in that i have nfi how to 'abolish the _' while making nested conditionals still work. ☝︎
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: so draw it.
asciilifeform: feel free to submit a patch.
asciilifeform: however the _ can be made to disappear, at the cost of an added moving part. i will ask ben_vulpes to draw this moving part, as exercise.
asciilifeform: this is an engineering tension, ben_vulpes ; i'll grant that the trailing _ is ugly. however it makes the mechanism simpler, all { are handled in exactly same way, and ditto all }
asciilifeform: !A .1{[foo]}{[bar]} Q
asciilifeform: !A .1{[foo]}{[bar]}_ Q
asciilifeform: ben_vulpes really hates typing '_' or wat
asciilifeform: !A .0{[foo]}{[bar]} Q
asciilifeform: !A .0{[foo]}{[bar]}_ Q
asciilifeform: !!up pehbot
asciilifeform: ben_vulpes: hm ?
asciilifeform: lolyes
asciilifeform: 'Stay connected, chat from anywhere, and never miss a message.'
asciilifeform: what makes you think it's a bouncer, ben_vulpes
asciilifeform: neato mod6 . thx for putting in the sweat.
asciilifeform: anybody try ?
asciilifeform: btw what does trb's ssl do with crafted der-encoded derpery ?
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: (until patched.)
asciilifeform: however with the 0day -- might be doable.
asciilifeform: ( uefi dun get read until close to end of warmup process )
asciilifeform: which you naturally can't do from bios.
asciilifeform: trinque: dun help with bios-jtagging tho. it gotta be disabled AT RESET
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: http://btcbase.org/log/2016-10-14#1555295 << re:. ☝︎
asciilifeform: in other lulz, http://seclists.org/fulldisclosure/2018/Jan/12 >> ahahahahahaha the amd fritz chip, apparently finally killed
asciilifeform: !A .1.0*#
asciilifeform: ( 1st looks like http://btcbase.org/log/2014-02-19#517160 . ) ☝︎
asciilifeform: this one -- went the 2nd.
asciilifeform: there's 2 ways those go.
asciilifeform: signed, i suspect, what was put in front of him to sign, without even reading.
asciilifeform: ( h. martin )
asciilifeform: fell over like a bowling pin after 'shown instrments'
asciilifeform: old bureaucrat, unpopular ( perhaps ) at office, picked as scapegoat for the infector leak of that year
asciilifeform: mircea_popescu: it's an autogenned item, aha
asciilifeform: in fact, if we weren't planning to take gpg behind the shed and shoot it, i'd publish my keyring-abolition patch ( gpg then DEMANDS pubkey FILE on cmdline for any op that uses one. ditto privates. )
asciilifeform: i don't want to see it. ever. if i'm seeing it, vtron is broken !
asciilifeform: see, asciilifeform's orig trick with tmp was ~specifically~ to abolish the gpg keyring nonsense
asciilifeform: wait why is it mb of shit
asciilifeform: user should not have to look in tmp.
asciilifeform: rather than rubbish left in tmp
asciilifeform: this corpus should consist 100% of stderr output.
asciilifeform: ... or make own.
asciilifeform: ( i do not know from memory, what perl's is )
asciilifeform: afaik the best known solution is the one i used -- use the script lang's purpose-made lib for the item
asciilifeform: for so long as vtron uses gpg shell-out, it's stuck with the tmp dir crapola
asciilifeform: mod6: you can't make sure that the mains cord dun get pulled mid-press either
asciilifeform: ( thinkaboutit, tmp would be entirely useless if this were not so )
asciilifeform: if you have a handle to it, it dun get zapped
asciilifeform: mod6: afaik this dun actually happen on any known unix
asciilifeform: mircea_popescu: aha!
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
asciilifeform: mod6: it makes, e.g., parallelly running vtrons on same box, impossible
asciilifeform: mod6: the most serious bug is not even the failure to delete the tempdir, but that every run of the vtron uses ~same one~
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: aha.
asciilifeform: ^ preview/puzzle pre-ch6. solve what X does.
asciilifeform: !A .BE7EA8B353CF33FA1226E6F87F97CE980353879CA9F00107C2DE4E123ECBE000.7D2AF9FAA2CD4F3CCFE8489B9BE1FE5F3A600D4E1E72A7C0041F0B793848FB2F.FA55F3F5459A9E799FD0913737C3FCBE74C01A9C3CE54F80083E16F27091F65F X #
asciilifeform: !!up pehbot
asciilifeform: speaking of...
asciilifeform: ok that'd be a platonic plaintextitude, lol, not a physical item.
asciilifeform: it's rather like... ffacalc, lol
asciilifeform: single yes.
asciilifeform: ( or heapless. consider, where do the external symbols get pulled from . )
asciilifeform: dunno that the meat parser is stackless