log☇︎
27500+ entries in 0.004s
asciilifeform: that's yet a third derp, whoever wrote python-gnupg
asciilifeform: mircea_popescu: presumably cuz koch stuck a gpl sticker on it
asciilifeform: i'll be happy to see'em sitting on neighbouring stakes tho
asciilifeform: mircea_popescu: stallman has plenty to answer for, but i dunno what he has to do specifically with koch's gpg
asciilifeform: ( and currently stepping on erry possible gnu.nail )
asciilifeform: mircea_popescu: funnily enuff happens to be exactly what asciilifeform's doing
asciilifeform: http://p.bvulpes.com/pastes/UOTkS/?raw=true
asciilifeform: phf: np
asciilifeform: ( i need specifically both vtrons to work on these boxen , with no systemwide modifications )
asciilifeform: but gotta find a pill, cuz right nao wheels turning in the mud
asciilifeform: no i get it
asciilifeform: still remains to be seen
asciilifeform: mircea_popescu: atm i'm not even in a place where i can say who's what is buggy
asciilifeform: seems like the closest thing to a working keccak-vtron currently is phf's v98 tho
asciilifeform: i was able to regrind ffa today, using phf's vdiff, but atm cannot yet press and confirm that it actually presses to same thing as the classical
asciilifeform: phf: fwiw my orig v.py is pretty sad in several wellknown ways -- i'm not particularly attached to it, would happily take mod6's, if there were (did i miss??) a ver of it patched to work in keccak
asciilifeform: with all respect to phf -- it seems to me that he's the one with the nonstandard envir
asciilifeform: really, nobody ? why is it that nobody until phf's v98 felt inclined to change the routine, then ?
asciilifeform: so loox like i'll be going with button 'a' .
asciilifeform: i will not be answerable for a 3GB ball of shit, there aint even 1% of the necessary hrs to read it, left in my lifespan
asciilifeform: i wrote ~10kb proggy, not 3GB.
asciilifeform: it's nonsense tho.
asciilifeform: by that token it's 3GB cuz that's how much stripped gentoo weighs, lol
asciilifeform: and 10xuple its mass
asciilifeform: it'd be ugly as sin
asciilifeform: phf: i dun want to glom python-gnupg into vtron tho!
asciilifeform: i can't think of anyffing to do but a) make flensed version of phf's that actually worx here, i have NO intention of breaking my legacy toolchain in which i still have 90000 unconverted private patches or b) bake an e.g. if gpg.__version__ = phf : ... else .... thing
asciilifeform: ugh
asciilifeform: phf: can you plz remind me why you changed that routine to begin with ?
asciilifeform: my orig worked with 0.3.2 ( which is poured into cement and i have no intention to 'upgrade' wtf lol )
asciilifeform: ok...
asciilifeform: 0.3.2
asciilifeform went to strace to find what gpg binary it actually invokes, and oddly enuff no mentions of EITHER in strace output...
asciilifeform: so apparently gpg2ism is not the culprit
asciilifeform: phf: worx -- in the sense that no above eggog : but same result as previously, http://p.bvulpes.com/pastes/wmR7H/?raw=true
asciilifeform: it always baked a tmp to satisfy gpg's keyring idjicy and nuked it after
asciilifeform: mircea_popescu: v.py never used keyring
asciilifeform: apparently not in my ver, grr
asciilifeform: '
asciilifeform: TypeError: __init__() got an unexpected keyword argument 'binary
asciilifeform goes to try mircea_popescu's tip
asciilifeform: loox like i'ma have to strip out the subkey garbage, and regenesis, 'v98-that-actually-worx'. unless phf has better idea.
asciilifeform: it worked!!
asciilifeform: ( on , afaik, all known kochian gpg )
asciilifeform: and yes it was originally my kludge. but the diff is, mine worked...
asciilifeform: really oughta be entirely homedir-local.
asciilifeform: and imho it is pretty sad that a vtron even sees ~anything~ 'systemwide'.
asciilifeform: phf: well that aint what i have here.
asciilifeform: lol
asciilifeform: phf: it will be even gnarlier, would have to parse the output somehow and essentially recreate all of python-gnupg ( wanna ? )
asciilifeform: what i'd like is a pill that is guaranteed not to break ANYTHING else.
asciilifeform: bvt: i am EXTREMELY reluctant to touch any of the portage knobs, these boxes are 'dried in amber' .
asciilifeform: ( alternatively, does anybody know how to control the gpg binary that python-gnupg sees ? )
asciilifeform: can somebody plz confirm that v98 ( as it appears in http://barksinthewind.com/2018/vpy-updated-for-vtools/ ) actually worked somewhere ?
asciilifeform: i dun have any cuntoo boxes here yet. all of my dev machines run vintage gentoo, where the gpg that python-gnupg sees is gpg2 (cuz idjit portage pulled it in, long ago). asciilifeform's actual pgp-ing happens on diff machine, naturally, with 1.4.10 . but apparently phf's hack for subkeyism breaks the thing in this combo.
asciilifeform: tho i'm beginning to suspect the culprit :
asciilifeform: !Q later tell phf for that matter, it does same thing! with yours! pray tell how didja even test the v98 thing, on what.
asciilifeform: !Q later tell phf http://btcbase.org/patches/v98#L74 leads to http://p.bvulpes.com/pastes/WhT97/?raw=true on (apparently all) boxes containing asciilifeform's pubkey
asciilifeform: aite
asciilifeform: ty diana_coman
asciilifeform: right. but i'm regrinding ch1-11 into keccak. ought manifest only to live in ch12 ( 11 technically had one, but it was adhoc, and not conformant to current formulation ) ? or in all ch1-11
asciilifeform: currently looking into how diana_coman did it
asciilifeform: imho also. the q is what's the most accurate , given that orig had no manifest
asciilifeform: but no, somehow gotta barnacle on orig.
asciilifeform: imho if the franks, or the visigoths, want diff sorting order when alphabetizing, they oughta have proclaimed a FSCII and VGSCII etc
asciilifeform: ( observe, the WHOLE fucking problem ascii standard was meant to solve, quietly got 'reopened' by the unitards )
asciilifeform: whichever
asciilifeform: lol, err, z/q
asciilifeform: 'here in sheepfuckistan, q goes before z' or somesuch
asciilifeform: i expect it was a concession to the french or some other barbarian tribe
asciilifeform: there aint any real sense behind the 'locale' nonsense imho
asciilifeform: it's gnudiff that spewed ~random order.
asciilifeform: phf: right
asciilifeform: originally i was gonna simply regrind ( by running through new vdiff ) ch1-11, and invite reader to hand-diff if he likes and see that only hashes have changed. but then noticed that the new vdiff also processes files in different order, so this won't give clean 'only hashes' diff. so thinking, may as well retrofit manifest to each of ch1-11
asciilifeform in the process of keccakizing ffa, hence practical q
asciilifeform: mircea_popescu: quite unrelatedly, what's your recommended formula for 'manifest' in keccak regrinds ? ( i.e. to retrofit manifest to ancient stuff, or only to latest v cut of it ? and with current blockheight, or to somehow estimate the one at the time of original publication ? )
asciilifeform: where is the comicbook wall in the bg ?
asciilifeform: mircea_popescu: a+++ headerface
asciilifeform: diana_coman: neato
asciilifeform: certainly if compared to 'freechoice'landia folx.
asciilifeform: fwiw asciilifeform's progenitors were matched up via the above algo
asciilifeform: we're from neighbouring, if you will, home planets. ☟︎
asciilifeform: of course they'd try
asciilifeform: even on asciilifeform's home planet, good chunk of marriages were 'soft-arranged' -- i.e. 'comrade colonel, you have a bachelor son, i have a ripe daughter' 'comrade lt colonel, let's box'em in a room, wainot' ☟︎☟︎☟︎☟︎
asciilifeform: this one's somehow not a mystery to good 80+% of globe
asciilifeform: well yes, notice asciilifeform did not say ' eh shined boots, who needs'em '
asciilifeform: lol i thought it was 'keep boots shined or else'
asciilifeform: picture if an accountant were to walk into an ameri-board with tally of the ~actual~ cost of running winblowz.
asciilifeform: power co.'s calculate resistive losses on high voltage lines, but for some peculiar reason no one (afaik) ever tallies up the real-life cost of this idjicy.
asciilifeform: http://jkorpela.fi/chars/c0.html << likbez re orig ascii controls.
asciilifeform: they were meant to be terminal and link control chars. i.e. exactly analogous to what html abuses < , >, &, for
asciilifeform: imho still nuttery, and tremendous waste.
asciilifeform: and yes i know 'why' they aint used : 'but oh oh, what if someone is on a SLIP modem!11'
asciilifeform: this leaves 25 that ~nobody uses for anyffing !
asciilifeform: well, + cr; 7
asciilifeform: or fughet even 8th bit, there's 32 control chars in ascii ! and space, nl, tab, del, ff, and null, account for only 6 !
asciilifeform: *hieroglyphs
asciilifeform: but no, gotta be hiroglyphs?
asciilifeform: why not use that 8th bit of the byte for something actually constructive...
asciilifeform: http://btcbase.org/log/2018-11-12#1871482 << i find it interesting that uniturdism is ubiquitous, but html etc is still stuck poaching perfectly ordinary 'telex' characters (i.e. found on keyboard) as 'magic' values ☝︎