Show Idle (> d.) Chans
← | Results 17751 ... 18000 found in trilema for 'f:ben' | →
ben_vulpes: lol even vex has commentary on the dccpisode
ben_vulpes: also how is 40M too large for a webserver?
ben_vulpes: !up renart
ben_vulpes: am i authed or not
ben_vulpes: mother shit fucker
ben_vulpes: !up renart
ben_vulpes: which yes, i'd complain of as well
ben_vulpes: erc complains of :host 0.0.0.199
ben_vulpes: asciilifeform: how big *is* it?
ben_vulpes: i don't think erc actually worx.
ben_vulpes: eh maybe thirtee.
ben_vulpes: perhaps only ten for me.
ben_vulpes: motherfucker.
ben_vulpes: asciilifeform: do please to dcc again
ben_vulpes: thank you for pointing out the inadequacy of everything.
ben_vulpes snaps a laptop
ben_vulpes: a gpggram would be lovely, or a .tgz i can scrape down from your server
ben_vulpes: dcc scares me
ben_vulpes: share a ware?
ben_vulpes: asciilifeform: joy of deficit spending here is that i complain about price of bits and find they're free.
ben_vulpes: ask me how many fuxx i give when trying to wire patches
ben_vulpes: yes yes, gnudiff is retarded
ben_vulpes: i'm always interested in finding the root nodes the 'further say'ers metastasized from
ben_vulpes: i will continue to drive for "reference implementation" over "real bitcoin" or such grandiosities
ben_vulpes: perhaps reference Bitcoin implementation instead of daemon, as daemon refers to how a process gets handled by whatever nix is handling procs locally
ben_vulpes: nifty, BingoBoingo
ben_vulpes: still working through scip, and even that's deficit spending.
ben_vulpes: but no, i am a classically poorly-read american.
ben_vulpes: i did debord a while ago
ben_vulpes: what 'it'
ben_vulpes: i don't know anything about the topic!
ben_vulpes: that'd be a no then?
ben_vulpes: guattari*
ben_vulpes: mircea_popescu: know anything about deleuze and guatarri in the context of intertextuality?
ben_vulpes: those curly horns don't look too fun, but whaddoiknow
ben_vulpes: the notion that there is any price for bits not agreed upon by a bid by people who want the bits and an opening of the floodgates by those who have them at an accepable rate is utter horseshit.
ben_vulpes: I WILL NOTE
ben_vulpes: seventy six eighty on MOTHERFUCKING KINDLE?!
ben_vulpes: a hundred and eleven fucking dollars!?
ben_vulpes: although that's probably more accurately strictly a SBCL thing.
ben_vulpes: one of the things that remains a mystery to me is the recompilation facilities supporting slime et al
ben_vulpes: did not know that tear ducts could weep blood
ben_vulpes: i've been trying to read the tinyscheme sources
ben_vulpes: trumpenreich 2016, duh
ben_vulpes: mircea_popescu wut?
ben_vulpes: works if you work it
ben_vulpes: you've been in it for what, 2 months at this point?
ben_vulpes: how was the 12/12
ben_vulpes: good evening, BingoBoingo
ben_vulpes: and thank you for reporting per my ask.
ben_vulpes: thank you jurov!
ben_vulpes: sorry for all the dumb questions, just working to tease out into explicitude what everyone else takes for granted.
ben_vulpes: sure, and i don't take much umbrage at this.
ben_vulpes: where c, c' and c'' all depend on b. if i press c, do c' and c'' make it as well?
ben_vulpes: a b {c, c', c''}
ben_vulpes: but the primes, do i press them? or simply recurse up the antecedent chain cleanly?
ben_vulpes: yes i follow, slow as i am
ben_vulpes: what is to be done with c' and c'', then (patches that also depend on b but have nothing to do with c)
ben_vulpes refuses to give up
ben_vulpes: BECAUSE FLATTENING TREES
ben_vulpes: but there's no guarantee that it renders a b c d e instead of d e a b c
ben_vulpes: flow already makes this mistake iirc
ben_vulpes: as is a
ben_vulpes: d is level 0, actually
ben_vulpes: howzabout another scenario
ben_vulpes: this was a thing i bounced off weeks ago!
ben_vulpes: conflict *with
ben_vulpes: mircea_popescu: this introduces a conflict between "pressing a head presses all signed patches at same leaf-level that have been signed by wot"
ben_vulpes: i think it's asciibeterministic
ben_vulpes: mhm, i recall
ben_vulpes: either that or find roots first, toposort from each root, and then apply each set of toposorted patches in some arbitrary order
ben_vulpes: i suspect v's toposort will need to account for multiple geneses
ben_vulpes: phf: what do you mean "first seen nodes"?
ben_vulpes: this is a nifty patchbrowser, phf
ben_vulpes: felipelalli: mpex doesn't respect key expiration extension.
ben_vulpes: phf: the chains must kiss somewhere in order for the ordering to make sense
ben_vulpes: phf: yuuuup.
ben_vulpes: ;;later tell asciilifeform ^^ plz to opine
ben_vulpes: so that operators can press, migrate dir, and press more.
ben_vulpes: eg that `v press shiva stans_sweet_patch.vpatch && v press shiva stans_sweet_patch.vpatch' must result in the same tree as running the command once.
ben_vulpes: this means that v-pressings have to be idempotent.
ben_vulpes: a thing to do might be to leave the genesis press as-is, move the resulting tinyscheme dir into the correct shiva location and then press the rest of the patches reground to reference the shivadir
ben_vulpes: phf: i see
ben_vulpes: but it's so close! with only an unknowable amount of further hacking it could totally work!
ben_vulpes: asciilifeform: has blessed us with a new root node with which to fuzz all v implementations
ben_vulpes: don't know or care
ben_vulpes: have fun
ben_vulpes: "naked Natalie Wood"
ben_vulpes: with that spittoon
ben_vulpes: have fun boys
ben_vulpes: mircea_popescu: highlights "uppose if we were all mentally retarded a la United States / Some O"
ben_vulpes: phf: also, if you'd care to share your llvm/clang compilator i'd love to take a look
ben_vulpes: mircea_popescu: link me?
ben_vulpes: phf: selection works on chrome for me
ben_vulpes: asciilifeform: would you confirm that tinyscheme_genesis_fixed.vpatch does *not* depend on shiva parts one and two?
ben_vulpes: i even pointed that one out to you, but we're mad busy
ben_vulpes: don't even add up to a whole computer over the year.
ben_vulpes: diapers are pretty cheap, actually.
ben_vulpes: how do you think i'd rather spend my dollars, on 'macbook pros' or bitcoins and linux workstations?
ben_vulpes: mircea_popescu: you think i don't know this?
ben_vulpes: la serenissima might be able to rent my oar pullers if it could convert my deficit spending to turkey-buying dollars
ben_vulpes: "viewing, not yet."
ben_vulpes: "selecting works!"
ben_vulpes: that's how mod6 has always quoted things...
ben_vulpes: but there's no actual reason why they couldn't mine high-s transactions, adherence to party line aside.
ben_vulpes: i'm sure that i misunderstand.
ben_vulpes: this'd invalidate the signature.
ben_vulpes: it is greater on malleated transactions?! but but
ben_vulpes: how do the miners benefit though.
ben_vulpes: could just as easily be a USG FUD campaign.
ben_vulpes: > deeply unclear
ben_vulpes: how did you come to the conclusion that it was miners doing the malleation, and not nobodies malleating and rebroadcasting?
ben_vulpes: uh next
ben_vulpes: but digging as far down into the roots of my conclusions as makes sense to dispel ambiguity
ben_vulpes: sure, i'm mostly confirming my own recollection.
ben_vulpes: now were b,tmsr~ to run its own pool mining only high-s transactions, would clients in the wild reject those blocks?
ben_vulpes: okay.
ben_vulpes: now, are miners not mining transactions signed low?
ben_vulpes: great, i follow.
ben_vulpes: (create and broadcast)
ben_vulpes: correct?
ben_vulpes: i create a transaction with a low s value. someone listening to broadcast transactions can rewrite my tx to have a high s value.
ben_vulpes: so a decomposition then
ben_vulpes: if you have access to the gradebook...
ben_vulpes: in that it's possible to malleate in either direction. ease i suppose doesn't figure into the question.
ben_vulpes: mircea_popescu: meaning that transactions can only be malleated from high->low order?
ben_vulpes: can someone confirm that it's just as possible to malleate a transaction low->high s as it is to malleate it high->low ?
ben_vulpes: anyways, mod6 you gotta upgrade v.pl to press *all* reachable leaves. that's the problem i'm running into with asciilifeform's recent shiva rebake
ben_vulpes: aha i begin to see the wisdom of pressing all reachable leaves now
ben_vulpes: asciilifeform: if i understand the shiva rebake correctly, applying tinyscheme_genesis_vpatch, then tinyscheme_crud_snip, then tinyscheme_repl_fix_fixed bangs the tree into the correct shape?
ben_vulpes chuckles
ben_vulpes: thanks for confirming mod6
ben_vulpes: that's what i thought
ben_vulpes: well there is a line break between those two strings
ben_vulpes: so the '.' is both a line-break escape and string concatenation?
ben_vulpes: yessir
ben_vulpes: http://log.bitcoin-assets.com/?date=31-01-2016#1391245 << lines 64 and 65 of v.pl. perhaps i can't read perl?
ben_vulpes: yeah boss
ben_vulpes: okeee
ben_vulpes: so if i press those individually, in order, they work. but if i press the last patch, i believe that it fails to find its antecedents.
ben_vulpes: the rebaked ones?
ben_vulpes: !s bug for you
ben_vulpes: the 'rebaked' ones.
ben_vulpes: did you get a chance to repro the issue i ran into with asciilifeform's shiva patches?
ben_vulpes: http://log.bitcoin-assets.com/?date=31-01-2016#1391110 << i did, not saying that it's not lying through its teeth though: http://imgur.com/Y1tGvZC
ben_vulpes: entirely unrelatedly, can anyone corroborate the story of the russians who burned a shitton of usd on camera and got the then-fed to credit some domestic account or other?
ben_vulpes: how many rickety fucking buckets of others' design must a man endure before he gets the fuck out and walks on his own feet is the question i'm endeavoring to resolve for myself
ben_vulpes: boundedness?
ben_vulpes: FIGHT
ben_vulpes: adlai: i don't know shit, frere, i just drag in dead birds for the adults to dispose of.
ben_vulpes: asciilifeform: this is for a motherfucking crystalspace project
ben_vulpes: http://log.bitcoin-assets.com/?date=31-01-2016#1391028 << i wonder what 'not making the cut' looks like these days. not willing to burn ones youth on the pyre of tenure-track whoring?
ben_vulpes can hear the retching from here
ben_vulpes: has 'really great cpp interop'
ben_vulpes: nooo, llvm bytecode.
ben_vulpes: if you have information to the contrary...
ben_vulpes: asciilifeform: i believe clasp is a standards-compliant commonlisp
ben_vulpes: because i want to press "shiva" into a tree that doesn't have, say, malleus_mikehearnificarum
ben_vulpes: reheheally?
ben_vulpes: my wot, mon trezor!
ben_vulpes: wot wot
ben_vulpes does not nod
ben_vulpes: ;;later tell pete_dushenski another translation challenger appears: http://trilema.com/2010/inca-o-pozitie-sexuala/
ben_vulpes: has the unexpected advantage of making alf barf
ben_vulpes: it nominally offers a lot over standard cl cffi, but i have not verified that myself.
ben_vulpes: http://log.bitcoin-assets.com/?date=31-01-2016#1390963 << look into clasp then, i'd just started digging into it when asciilifeform released shiva
ben_vulpes: diana_coman: no hard requirement, sure, i just imagine that replacing the crystalspace client's going to be no small pile of reverse engineering. i say this knowing nothing about the cs server/client software relationship.
ben_vulpes: asciilifeform plans to use it to inspect memory of running bitcoinds in real time
ben_vulpes: diana_coman: i doubt you'll move the client away from cpp, but tinyscheme is a potential route to embedding scheme /in/ the existing client.
ben_vulpes: ;;later tell diana_coman ^^
ben_vulpes: ;;later tell jurov and eulorans et al you might want to look into this tinyscheme thing
ben_vulpes: http://therealbitcoin.org/ml/btc-dev/2016-January/000201.html << i swear i saw some mentione of this earlier but cannot find it now. for those playing along at home, the sig name for these patches that will please v.pl is <patchname>.vpatch.<signatory's_wot_handle>.asc
ben_vulpes: ah wait no that wasn't ak47.sh
ben_vulpes: punkman: you could always contribute to b,tmsr's deficit by standing the jenkins instance up yourself.
ben_vulpes: scripting the whole process in the context of "continuous integration servers" is nifty, but finding the noob caltrops is also important.
ben_vulpes: dunno man i don't actually think it's of much value. having actual humans in the actual wot build things is much more important.
ben_vulpes: this was god i don't know how many months ago
ben_vulpes: funnily enough i just nuked its builddir
ben_vulpes: a full sync of each bitcoind produced by each patch sent to the ml
ben_vulpes: trunk*
ben_vulpes: another entry in the long list of things i've written that never made it into the truck
ben_vulpes: never for battle
ben_vulpes: a well polished bash turd
ben_vulpes: and buildroot handily obsoleted ak47.sh
ben_vulpes: v.lisp has just been languishing on the island of poorly written and embarassing software
ben_vulpes: i shut the jenkins down because full syncs of each patch was prohibitively resource and time intensive and parallelized poorly
ben_vulpes: or ak47.sh?
ben_vulpes: punkman: jenkins? or v.lisp?
ben_vulpes: probably any non-vpatch file'd do the trick.
ben_vulpes: ;;later tell mod6 stick a random file with .html suffix in the patches dir to reproduce the stale gnupg dir big
ben_vulpes: this is probably a purposes and causes thing, huh. avoid working towards the purpose of usable software for other people, and proceed from the cause of "hell is other people's code"...
ben_vulpes: is everyone who hacks on this thing to write and use their own vtronic cockpit controls? or is the production of /a/ vtron usable in other contexts a goal?
ben_vulpes: i am struck by a question i find interesting
ben_vulpes: ;;later tell mod6 alternatively, consider using mktemp -d
ben_vulpes: ;;later tell mod6 i got v.pl into a weird place where it didn't clean up its gnupg tempdir. perhaps consider using an "exit_gracefully" function where you're currently simply "die"-ing.
ben_vulpes: nifty
ben_vulpes: ever share it?
ben_vulpes: punkman: vit's a v.py descendant, correct?
ben_vulpes: well one is prefixed with the stupid unix hidden-file/dir period convention
ben_vulpes: unrelatedly, while we're ripping the rug out from under mod6, is there a good reason to continue with the inconsistent directory structure of `./.seals' and `./patches'?
ben_vulpes: punkman: "he's a good man, and thorough"
ben_vulpes goes digging through the gui for "never ever fucking toss my scrollback option"
ben_vulpes: but this fucking term just lost my motherfucking scrollback, because people reinventing wheels for os x have no historical context
ben_vulpes: pete_dushenski: nah, because i get "good signature from korsgaard"
ben_vulpes: punkman: by my read 'rebase' as mircea_popescu uses it means 'dump into the v tree'
ben_vulpes: "gpg: WARNING: not a detached signature; file `buildroot-2015.05.tar.gz' was NOT verified!"?
ben_vulpes: has anyone else noticed the following when using build-bitcoind-9999*K.sh?
ben_vulpes: yo mod6 what does it mean in perl to do my $var = "string" . \n "otherstring" is the period a linebreak escape in perl, and the variable implicitly a concatenation of the two strings?
ben_vulpes: http://www.northofreality.com/secrets/ << bit of a shame that aramcheck's not in the wot and on patreon, i like his weirdfic.
ben_vulpes: what is "the leyla black"?
ben_vulpes: mircea_popescu: i'm using trinque's experimental makefiles.
ben_vulpes: build-bitcoind-whateverk.sh?
ben_vulpes: ;;later tell trinque i may be exceptionally retarded today, but is there a reason why shit/Manifest.sha256 doesn't contain a hash for buildroot?
ben_vulpes: i'm just fumbling in the dark
ben_vulpes: i'm struggling to build a cohesive mental model for the right way to approach this gordian knot
ben_vulpes: asciilifeform likes to scream about how dumb the keyring is
ben_vulpes: ;;later tell trinque hey buddy looks like your makefiles depend on keys in the personal keyring
ben_vulpes: mod6: do you expect me to have korsgaard's key in my personal keyring when running build-bitcoind-V99996K.sh?
ben_vulpes: > read buildroot
ben_vulpes: so what is the thing to be done with korsgaard's key?
ben_vulpes: hey, stan's bouncer died!
ben_vulpes: deedbot.org script mentioned above i believe uses asciilifeform's old key
ben_vulpes: some truth in it.
← | →
Random(trilema) | Download hourly DB snapshot | Get Source Code