Show Idle (> d.) Chans
← | Results 36001 ... 36250 found in trilema for 'f:ben' | →
ben_vulpes: quite likely.
ben_vulpes: check my arrival date in -assets
ben_vulpes: no sir
ben_vulpes: your book, sure.
ben_vulpes: surely it's not that easy
ben_vulpes: $ cp ~/.bitcoin ~/.bitcoin-test && ./ancient-bitcoind -datadir ~/.bitcoin-test ?
ben_vulpes: <mircea_popescu> 0.5.6rc3 works << enhanced sync speed?
ben_vulpes: this is where docker starts coming in handy: instead of burning many hours on chasing down platform and architecture details to get the thing to work on os x, i'm leaning towards just running 0.5.3 in a VM.
ben_vulpes: i also think that building on os x is a bad idea
ben_vulpes: i am considering bisecting the codebase for building on os x
ben_vulpes: just curious
ben_vulpes: i ain't picking up shit
ben_vulpes: asciilifeform: what in place of bdb?
ben_vulpes digs spare hdd out of closet for aux blockchain
ben_vulpes: slow sync, myriad crapolade
ben_vulpes: i'm going for 0.5.3
ben_vulpes: asciilifeform: what release are you targeting?
ben_vulpes tries it again
ben_vulpes: ALSO STILL VULNERABLE TO SHELLSHOCK
ben_vulpes: another reason this damn platform's doomed
ben_vulpes: getting command line functionality on os x has been a headache every time i tried it
ben_vulpes: also also also also
ben_vulpes: nubbins i was just opining
ben_vulpes: oh sorry
ben_vulpes: wallet retardation gets cut or reimplemented non retardedly
ben_vulpes: qt gets cut
ben_vulpes: molding bullets...
ben_vulpes: mod6: which deps?
ben_vulpes: ergo, qt. at first, at least.
ben_vulpes: but when you're taught that the right solution to all problems is to do it by hand, with the tools handed one by authority, unlearning that is hard
ben_vulpes: not at all
ben_vulpes: constraint problems, too?
ben_vulpes: i: solved quadratics by hand because programming solvers was taught to me to be cheating
ben_vulpes: you: grew up on lisp machine lore
ben_vulpes: well, consider all the things i've been unlearning
ben_vulpes: but i don't see any roadblocks at this time.
ben_vulpes: i still depend on the qt client. need to come up with a workflow that works for the 0.5.3 client.
ben_vulpes: i'm transitioning backwards asciilifeform
ben_vulpes: <mircea_popescu> anyway, the consensus seems to be 6.3 ? << i've yet to hear a compelling argument for anything past 0.5.3
ben_vulpes: although let's be clear, i was just browsing the release notes. if there were breaking changes merged in since then, this'd be a lulzy way to surface them.
ben_vulpes: <othernubs`> ben_vulpes, speaketh << nothing strictly necessary post 0.5.3
ben_vulpes: yeah i'll take free credit for no work
ben_vulpes: hussling? is this some odd mix of hassling and hustling?
ben_vulpes: functional inputs vastly more important though
ben_vulpes: mod6: lol "functional" as in the programming style or "functional" in that "kinda sorta mebbe works"
ben_vulpes: mod6: let me know what style inputs you have
ben_vulpes: pull the latest from cascadianhacker.com if you'd be so kind
ben_vulpes: mod6: i'd be thrilled if you'd test it for me. i've been testing it against an amazon image, but more eyes etc etc etc
ben_vulpes: mod6: it's what was in production during that 0.5.3 release
ben_vulpes: configuring instances by hand is not allowed, emacs or no
ben_vulpes: now that just goes too goddamn far i tell you
ben_vulpes: nail that sticks up gets smacked down, as the nips say
ben_vulpes: why so as to not get whacked
ben_vulpes: occasional 0.5.3 node may advertise itself as 0.9 for reasons of camoflauge
ben_vulpes: i think its sanely factored. far more so than pankakke's obfuscated bash competition entry.
ben_vulpes: i'd love your code review as well sir
ben_vulpes: yeah, take a look
ben_vulpes: it's not meant for curl2sudo broheims
ben_vulpes: what, is my personal site not adequate?
ben_vulpes: mod6: glad you like it!
ben_vulpes: decimation: how would one ever know?
ben_vulpes: they're running out of levers to drive adoption otherwise
ben_vulpes: my 0.5.3 node hasn't barfed yet
ben_vulpes digs through notes as well
ben_vulpes: decimation: why 0.6?
ben_vulpes: what is this, late bettor hour?
ben_vulpes: guessing after the reveal
ben_vulpes: no fith
ben_vulpes: commitments
ben_vulpes: deadlines
ben_vulpes: features
ben_vulpes: oop kakobrekla making product mistakes
ben_vulpes: i plead the fith
ben_vulpes: ah jesus what happened to my maths
ben_vulpes: unhackable
ben_vulpes: assbot must run on lisp machines
ben_vulpes: foo\amazingh
ben_vulpes: fooamazingh
ben_vulpes: foomazingh
ben_vulpes: gotta wait for the shartup to come along claiming "zeroth best amazingth" i guess now
ben_vulpes: i don't think these are exclusive
ben_vulpes: year 0
ben_vulpes: "the first year"
ben_vulpes: ;;calc 2014 - 2009
ben_vulpes: what d'you have for us, KayTheFlower?
ben_vulpes: say please and thank you
ben_vulpes: !up KayTheFlower
ben_vulpes: puts us in the fifth year of our savior satoshi
ben_vulpes: jan 3rd, 2009
ben_vulpes: block zero
ben_vulpes: can we start counting in years since the first coinbase yet?
ben_vulpes: irc.serenissima.butts when
ben_vulpes: pwahahaha
ben_vulpes: ;;ud french cleaning
ben_vulpes: look ma, problems?
ben_vulpes: rm -rf / solves all problems
ben_vulpes doesn't actually know c - the horror!
ben_vulpes: 1 warning, but i think it's fine: https://www.refheap.com/92127
ben_vulpes: xCXXFLAGS=....$(HARDENING)
ben_vulpes: HARDENING=fno-stack-protector -fstack-protector-all -Wstack-protector
ben_vulpes: kinda looks like that's in there already, jurov
ben_vulpes: -f-stack-protector?
ben_vulpes: jurov: what was the stack smashing you were talking about recently?
ben_vulpes: (as fine as the cpp bitcoin turd can be)
ben_vulpes: no it's fine absolutely fine everything is fine
ben_vulpes: i can paste for you.
ben_vulpes: no, it makes sensible output.
ben_vulpes: i have no idea what's actually *in* the thing.
ben_vulpes: the compiler poops a binary onto disk.
ben_vulpes: oh sorry, too much brevity.
ben_vulpes: no idea what's in the turd.
ben_vulpes: compiler poops
ben_vulpes: build passes
ben_vulpes: libqrencode-dev purged
ben_vulpes: but baby steps
ben_vulpes: all of a sudden i want to rip SSL out as well
ben_vulpes: no, leftover from my experiments with 0.6
ben_vulpes: later pete
ben_vulpes: updated with a blank assignation for UPNP: https://www.refheap.com/92126
ben_vulpes: i ripped the assignation line out entirely. later there's an ifndef that assigns it to the hyphen.
ben_vulpes: in the makefile?
ben_vulpes: so forgive my c makefile naivte, but is there a difference between an USE_UPNP= and just not declaring the variable?
ben_vulpes: later they introduced the hyphen, that apparently wasn't a thing at 0.5.3
ben_vulpes: well it builds quite happily.
ben_vulpes: i want to compile without it. period. full stop.
ben_vulpes: Apocalyptic: i'm reading in doc/build-unix.txt that the options are USE_UPNP=, USE_UPNP=0 and USE_UPNP=1
ben_vulpes: oh oh
ben_vulpes: Apocalyptic: do let me know if there's a good reason to keep UPNP in there.
ben_vulpes: do I?
ben_vulpes: rips out UPNP support.
ben_vulpes: it'd be neat if he'd differentiate between Bitcoin the reference implementation which is bug-ridden and shitty, and Bitcoin the protocol which doesn't exist.
ben_vulpes: ya there we go
ben_vulpes: but i keep coming back to "i only want to know the balances and histories of these addresses"
ben_vulpes: i'm trying to think of sensible use cases
ben_vulpes: "accounts" in btc wallets are kind of stupid, right?
ben_vulpes: still working through the changelog
ben_vulpes: decimation: i imagined something like that, yeah.
ben_vulpes does not actually understand how the infinite layers of the modern v.n. architecture does it's nasty business.
ben_vulpes: as opposed to BDB
ben_vulpes: was the blockchain written directly to disk at some point in the reference client's history?
ben_vulpes: i'm sure it matters to someone
ben_vulpes: "oh nine three"
ben_vulpes: and i never say the decimal
ben_vulpes: i'd probably say "oh nine", but i should write "a 0.9..."
ben_vulpes: i'm retarded, it's fine
ben_vulpes: ah hue
ben_vulpes: wouldn't it be "a zero"?
ben_vulpes: syllabic efficiency
ben_vulpes: if an 0.9 *node*...
ben_vulpes: if 0.9 says "this txn sucks!" but an 0.6 miner included it, this takes us right to a hard fork
ben_vulpes: no it's totally in the transaction processing rules
ben_vulpes: so: isStandard() - this is not related to blockchain and transaction processing rules, correct?
ben_vulpes: varnish is okay
ben_vulpes: "news" is all slant
ben_vulpes: ya got it
ben_vulpes: salad
ben_vulpes: all i have is the github repo
ben_vulpes: does anyone in la serenissima have a copy of the bitcoin repository of june 2012 vintage?
ben_vulpes: jurov: i'm just trying to build 0.6.3 the way it seems to want building
ben_vulpes: it would be expedient to download miniupnpc 1.6 from http://miniupnp.free.fr/files/ but what do to prevent mitm of that source?
ben_vulpes: am i reading this (https://packages.debian.org/squeeze-backports/miniupnpc) correctly? debian backports only has miniupnpc-1.5?
ben_vulpes: write-tracking os when
ben_vulpes: immutable os when
ben_vulpes: undata:
ben_vulpes: i see only abstractions that help manage one set of complexities while making more complexities.
ben_vulpes: undata: i see no security value add.
ben_vulpes: could be dog
ben_vulpes: <mircea_popescu> wait, so PinkPosixPXE is a GIRL ?!?!?! << this was not obvious?
ben_vulpes: from the derpotron: https://blocksign.com/
ben_vulpes: can't speak to the hasids or historically, but definitely in my experience.
ben_vulpes: asciilifeform: 'carry out the program' << yup.
ben_vulpes: kakobrekla: one can claim, but there's a trilema for that :P
ben_vulpes: it's been a decent tool for hacking mud, that's about all i know.
ben_vulpes: i'm getting the gist.
ben_vulpes: riskspace is foreign code on box, exploits of running processes from outside world?
ben_vulpes: just a few years ago i was building wafer hosts - there is much i don't know about websec.
ben_vulpes: would you enumerate the risks?
ben_vulpes: hm digitalocean doesn't even bsd
ben_vulpes: related to asciilifeform's "must fit in head" problem
ben_vulpes: i guess at a high level stupid solution to stupid problems.
ben_vulpes: for instance, different versions of the python imaging library for different services.
ben_vulpes: mircea_popescu, mats_cd03: ease of dependency management, resource isolation, cognitive overhead. i'm dumb and have to deal with crazy complex legacy shit that's most expediently put into 'containers for poor and time constrained engineers'.
ben_vulpes: <mats_cd03> too bad nobody wants to talk about how its horridly vulnerable << well enlighten my derpy ass
ben_vulpes: just cause
ben_vulpes: !up CryptOprah
ben_vulpes: how are you to fight the usg thusly?
ben_vulpes: <mircea_popescu> through which metaphore i am suggesting, of course, that coders are whores and money is a penis. << btc today, equity in thing of value mebbe tomorrow...
ben_vulpes: but -- digging nevertheless.
ben_vulpes: write some tests
ben_vulpes: booting is the first edge case
ben_vulpes: thanks, thestringpuller
ben_vulpes: so i'm not a a c professional by any stretch of the mind - where do the obj/*.o files come from?
ben_vulpes: pahahahaha
ben_vulpes: that's precisely what i was banging into.
ben_vulpes: good question
ben_vulpes: but uh
ben_vulpes: aforementioned libdb4.8-dev
ben_vulpes: because that was released ca. 2013, roundabout when 0.6 came out
ben_vulpes: considering using squeezy
ben_vulpes: wheezy
ben_vulpes: danielpbarron: i'm building a container with docker, and a cursory search turned up no docker base image for openbsd.
ben_vulpes: macos is its own crazy problem that I'm not about to impose on anyone.
ben_vulpes: nah, that's not what i'm doing.
ben_vulpes: BingoBoingo: specifically, 0.6.3 from source.
ben_vulpes: hm should i be doing this on debian 6?
ben_vulpes: here's an interesting nugget
ben_vulpes: but w/e/
ben_vulpes: hardly just a receiver then.
ben_vulpes: bidirectional
ben_vulpes: kakobrekla: please explain to me how you triangulate a receiver.
ben_vulpes: "This time it was encrypted but it was possible to determine the position of the transmitter and the reciever." << how would the latter part be possible?
ben_vulpes: slowly heating's supposed to do the trick
ben_vulpes: starfish is worth a sight more than that
ben_vulpes: can only afford hundredth-coin buys
ben_vulpes: mats_cd03: well you see i am an utter pauper
ben_vulpes: ;;ticker
ben_vulpes: thanks mats_cd03
ben_vulpes: ;;calc 0.03 * [[ ticker ]]
ben_vulpes: ;;calc 0.03 * [[ticker]]
ben_vulpes: ;;calc 0.03 * [[;;ticker]]
ben_vulpes winces at the memory
ben_vulpes: oh the core
ben_vulpes: ya, typo.
ben_vulpes: "kistmet", etc.
ben_vulpes: i prefer ancient history
← | →
Random(trilema) | Download hourly DB snapshot | Get Source Code