ben_vulpes: (emacs-gd, that is)
ben_vulpes: "trivial", i'm sure
ben_vulpes: irc bouncer implementation's a good thing to have in the interim.
ben_vulpes: decimation: re gossipd errything's gonna have to be reimplemented atop it
ben_vulpes: <cazalla> the irish have been flooding aussie shores for the past few years << ugh i met another ozzie today
ben_vulpes: ;;later tell mircea_popescu an irc bouncer job advert wouldn't go amiss
ben_vulpes: i'm saying that my nose ain't that good yet
ben_vulpes: oh you rejected it before you figured out that editing the config files while the thing waas running would fly it straight into the wall at 0.8 mach?
ben_vulpes: shit was wack.
ben_vulpes: i ran both znc and weechat as bouncers for a while
ben_vulpes: mhm
ben_vulpes: good with high latency, network-hopping, all of the travails of diginomad life.
ben_vulpes: but very good tool for persistent terminals on remote hosts.
ben_vulpes: mnno, not replacement
ben_vulpes: more liek an ssh-wannabe
ben_vulpes: but not a wm-wannabe
ben_vulpes: ah no, it's a tmuxalike
ben_vulpes: but it does new up a udp thinger.
ben_vulpes: can't say as i can tell from your question.
ben_vulpes: decimation: have you looked into mosh?
ben_vulpes: gentoo.
ben_vulpes: decimation: running more than one emacs chafes.
ben_vulpes: sitrep: freshly provisioned server builds boost, bdb and openssl w/out a hitch, barfs on compiling bitcoind because lacking i b'leev integer retardation patch
ben_vulpes: decimation: lmk if you come up with an acceptable bouncer situation.
ben_vulpes: jesus shit i blink and y'all crap out 400 lines?
ben_vulpes: and with the work they're *doubtless* doing on autonomous flugenatoms that's going to be some impressive air support
ben_vulpes: trinque: ah, i only meant to suggest that they might park an armada offshore to provide fire support.
ben_vulpes: same thing i said before, really.
ben_vulpes: a*
ben_vulpes: i can see them either filling a power vacuum or backing an secession.
ben_vulpes: and china's the only one of those two groups today with ships and ship-launched rockets with significant distance capabilities.
ben_vulpes: texas needs either zetas or chinks to hold its border to the north.
ben_vulpes: trinque: the rednecks will be the reason china gets involved.
ben_vulpes: trinque: ain't gonna be b.
ben_vulpes: hooer
ben_vulpes: ;;ticker
ben_vulpes: a liberal /myth/, jurov
ben_vulpes: global warming is a myth
ben_vulpes: (unrelatedly, whose moronic decision was it to produce keys that tab-complete before their public counterparts? looking at you, id_rsaa)
ben_vulpes: whereas in bsas, i could walk for an hour plus without feeling the burn.
ben_vulpes: and it's what - three blocks?
ben_vulpes: the stroll from office to tacos midday is almost guaranteed to pink me up a bit.
ben_vulpes: asciilifeform: i still marvel at that.
ben_vulpes: a forest fire even further north than i is smogging up the world
ben_vulpes is sitting under a red sun
ben_vulpes: you have the weirdest fetishes.
ben_vulpes: what's wrong with etags?
ben_vulpes coffees.
ben_vulpes: aha, missed that.
ben_vulpes: powers that be froze action, restarted game, provided script
ben_vulpes: asciilifeform: there was also the millenium challenge 2002
ben_vulpes: http://log.bitcoin-assets.com/?date=03-07-2015#1185652 << i really gotta post ak47.sh to the ml
ben_vulpes: ohai punkman
ben_vulpes: https://github.com/extempore/real-bitcoin << i keep the patches in their own directory
ben_vulpes: http://log.bitcoin-assets.com/?date=03-07-2015#1185611 << i keep a git repo on disk, i think someone else has one of these running in public as well
ben_vulpes: d'you mean that management is about "you may do XXX but not YYY" when you say "doors"?
ben_vulpes: howso?
ben_vulpes: eh, alf may actually get to the ada impl before a block v1 sticks again.
ben_vulpes: ;;later tell pete_dushenski king of the hill: "i sell cars and car backed securities"
ben_vulpes: shinohai: wanted to know about your 0.5.3.1's behavior during the phr0k
ben_vulpes: http://log.bitcoin-assets.com/?date=03-07-2015#1185459 << i don't think this addresses collusion.
ben_vulpes: wait gernika's new blood?
ben_vulpes: clearly you don't fight enough zombies
ben_vulpes: how convenient!
ben_vulpes: 1mb's too big already.
ben_vulpes: pete_dushenski: "i sell bitcoins and bitcoin-backed derivatives"
ben_vulpes: so's this phr0k the nail in 20mb blocks' coffin?
ben_vulpes: http://log.bitcoin-assets.com/?date=04-07-2015#1187606 << thank you! very cool.
ben_vulpes: http://log.bitcoin-assets.com/?date=04-07-2015#1187419 << this was *so* stupid.
ben_vulpes: <mats> alright << i'd love a read
ben_vulpes: midnightmagic: that's some wack ass disingenuous shit. you jumped in on the n block consensus line.
ben_vulpes: i thought you said you were reading logs!?
ben_vulpes: dumpblock, eatblock, exposure of the ancient blockchain is quiet now?
ben_vulpes: quiet!?
ben_vulpes: nah we seem to have defused the antagonism for now
ben_vulpes: <midnightmagic> ben_vulpes: Dude man, with the shit you guys say in here, I have no idea when you're ribbing someone, or promising a spear in the gut. :( << the ambiguity has to be completely intolerable
ben_vulpes: anyways, chickens run around with their heads cut off for minutes. what of it? they still lost to the butcher.
ben_vulpes: conflict is productive!
ben_vulpes: myeah
ben_vulpes: :P
ben_vulpes: yet
ben_vulpes: you're not in line for a stake
ben_vulpes: midnightmagic: re #trollfail it's supposed to be lighthearted elbows-in-ribs
ben_vulpes: why bang on about points that are already settled?
ben_vulpes: moreover, if the decisions made here trickle down to "bitcoin core", why should we pursue them further?
ben_vulpes: *derpboom*
ben_vulpes: so we won, and you want to 3/10 troll on the topic?
ben_vulpes: for a grand coup of shit-as-what-don't-matter?
ben_vulpes: midnightmagic: reddit? twitter? d'you want to roll medium and perhaps bitcointalk.org into that as well?
ben_vulpes: 6/10 #spergytrollfail
ben_vulpes: <midnightmagic> Once everyone else started, you stopped. How come? << hipsters always move on, boss
ben_vulpes: possibly*
ben_vulpes: <midnightmagic> Yeah, I mean aside from the grumbling in here which nobody but people *in here* seems to read. << how could you possible know
ben_vulpes: it's all well and good to say "strip out the components", i just don't buy that that's possible.
ben_vulpes: midnightmagic: no less wrong than what now?
ben_vulpes: decimation: no but you see we need to slurp the spitoon because if we don't something terrifying that we can't reason about won't happen!
ben_vulpes: <decimation> why wouldn't we want a static bitcoind that is correct for all time? << we do. midnightmagic does not.
ben_vulpes: midnightmagic: you were probably just on the cusp of killing hitler too.
ben_vulpes: bitcoinds*
ben_vulpes: this, i gather, is news to you.
ben_vulpes: bitcoind's built with openssl versions after 1.0.1g don't sync.
ben_vulpes: openssl changed behavior. bitcoin did not.
ben_vulpes: midnightmagic: art thou familiar with the 1.0.1g issue?
ben_vulpes: just the network. that, only that, no more, no less.
ben_vulpes: there's* just no window.
ben_vulpes: 's just no window.
ben_vulpes: this moronic 'acceptance-in-blockchain' algo doesn't work, because hashpower can revert and rewrite an arbitrarily-lengthed blockchain.
ben_vulpes: midnightmagic: you make this mistake of letting the plants control the conversation. "what's the right magic number of blocks to signal fork acceptance?" answer: there isn't. there is only the long-term behavior of the network.
ben_vulpes: i don't accept it either.
ben_vulpes: y'ever hear the line: "don't feed the trolls"?
ben_vulpes: lol and yet you bit
ben_vulpes: since when has midnightmagic's employer given a shit about profitability?
ben_vulpes: efficiency is not a prerequisite for fab runs.
ben_vulpes: midnightmagic is ready to work more student exercises?
ben_vulpes: decimation is ready to bet against diff increases?
ben_vulpes: lol 'integerial'
ben_vulpes: midnightmagic: this is a basic feature of integrals and curves.
ben_vulpes: euhue
ben_vulpes: another value for derpfiguration.
ben_vulpes: magic numbers and magic thinking.
ben_vulpes: decimation: srsly.
ben_vulpes: a midnightmagic
ben_vulpes: oh look
ben_vulpes: deedbot-: http://cascadianhacker.com/ph0rk.txt
ben_vulpes: anyways
ben_vulpes: those hafta be the 2 derpiest typos of my life.
ben_vulpes: http://therealbitcoin.org/ml/btc-dev/2015-July/000114.html << ahaha fattest fingers.
ben_vulpes: "reasons" being that i wrote a blog post saying "i don't think much happened after this"
ben_vulpes: trinque: whar deedbot
ben_vulpes: deedbot wru
ben_vulpes: ah fml
ben_vulpes: http://log.bitcoin-assets.com/?date=21-01-2015#985356 << this still hurts, every time i see it
ben_vulpes: ;;later tell gavinandresen ^^
ben_vulpes is amused, but not honored. if ye'd only had actual management once upon a time, this'd not be a notable achievement.
ben_vulpes: looks like the shitgnomes have been working overtime to address my complaints.
ben_vulpes was looking through recent "bitcoin-core" pull requests, found many integration testing scripts
ben_vulpes: an informal signoff from y'bosses would be nice before i deposit this in the white porcelain turdotron
ben_vulpes: must be considered-> is an
ben_vulpes: mod6, asciilifeform, mircea_popescu: http://dpaste.com/367HMKF.txt
ben_vulpes: ty, 1.0.1g
ben_vulpes: what was the version number of openssl we determined necessary to validate the full chain?
ben_vulpes: well this signature issue is tricky as shit already - openssl is already blowing up validating the chain with anything other than...
ben_vulpes: mod6: myeah entirely.
ben_vulpes is somewhat at sea w/r/t propaganda semantics
ben_vulpes: perhaps a hash of the codebase instead of the semver crap?
ben_vulpes: mircea_popescu, mod6, asciilifeform: i don't see a reason to make this much more than 25 words. do you think much detail or polemic is necessary here?
ben_vulpes: trinque: host it y'self.
ben_vulpes: this is almost as bad as defining a word with the word to be defined
ben_vulpes: "the chain that is the real chain is the chain that verifies under 0.5.3"
ben_vulpes: ugh man i kinda hate this
ben_vulpes: foar posterity and posteriors
ben_vulpes has never seen a reorg happen live
ben_vulpes: euhue
ben_vulpes: i'm nominally on vaycay but...panzer
ben_vulpes: check ur lawgz bru
ben_vulpes: there's a ph0rk in progress
ben_vulpes: i thought you were running a conformal impl somewhere
ben_vulpes: no no the conformal impl
ben_vulpes: how's btcd handling r4gn4phr0k?
ben_vulpes: ah mhm.
ben_vulpes: cp ~/.bitcoin.bak/
ben_vulpes: plz foar not to buhlete!
ben_vulpes: synced
ben_vulpes: trinque: do you have a RI up-to-date?
ben_vulpes: shinohai: you around?
ben_vulpes: meaning adopt the power ranger braindamage again?
ben_vulpes: "re-break"?
ben_vulpes: i want a man in the ground, i don't make that dependent on his wife squirting or w/e
ben_vulpes: asciilifeform: nodeps!
ben_vulpes: hey kakobrekla how much can i cram into a rating field?
ben_vulpes: one goddamn nail at a time
ben_vulpes: man all i can do is nail this coffin closed
ben_vulpes: ;;later tell lukejr listen you gotta stop it wiht this "i can tell miners what's right and wrong" bs
ben_vulpes: << lukejr
ben_vulpes: "Most likely this is caused by broken-by-design-for-profit mining code, but none of their stuff is open source AFAIK. Maybe more details will be known with time."
ben_vulpes: reddit, for all the silencing and muting of the actual bitcoin foundation, seems to be turning the corner on sense
ben_vulpes: ehueh
ben_vulpes: "
ben_vulpes: "They're not running full nodes because the current 500KB blocks are too big.
ben_vulpes: "
ben_vulpes: "Updating to the latest when what you have works is how you break things.
ben_vulpes: i never did anything, we all know that. joke's almost too easy.
ben_vulpes: :P
ben_vulpes: primarily, me.
ben_vulpes is also curious to see how much "political capital" the derpdation burns today
ben_vulpes: mircea_popescu: anyone can narrow the rules, but whether that's "bitcoin" is an open question.
ben_vulpes: T.I.A.S. (tm) (r) (#emacs)
ben_vulpes: too bad, fuck them.
ben_vulpes: things either validate under 0.5.whatever or they don't.
ben_vulpes: i've not yet accepted this soft/hardfork duality.
ben_vulpes: frantic action is for the impotent.
ben_vulpes: i have a porch of meatwot and babes that actually need attending to.
ben_vulpes: mod6 if you feel compelled to elaborate on this, go ahead.
ben_vulpes: Bitcoin 0.5.3 is the canonical reference implementation. If a fork occurs and one side validates on the 0.5.3 codebase while the other does not, the chain that validates under 0.5.3 is the only valid chain.
ben_vulpes: asciilifeform: translation plox?
ben_vulpes sighs
ben_vulpes: "Except BIP 66 received 95% support from the relevant group (miners). " << ehuehuehehueeueueueueueeeee
ben_vulpes: nigga pleez
ben_vulpes: so what, f2pool and phrenz dies next week?
ben_vulpes: simple rehash of the "let's probe network cohesion strength" fork
ben_vulpes: "The majority of hashing power is mining an invalid chain - it's not going to "win" - they're just wasting their effort." << euheuheuheuheuheheehueheuheuheehu
ben_vulpes: my position being "if your notion of a valid block has to patch 0.5.*, get fucked."
ben_vulpes: "However, this also means they're not checking the new BIP66 rule, and are now mining invalid blocks because of it. (another miner happened to create an invalid, non-BIP66 respecting block) If you're not using Bitcoin Core, you might be accepting transactions that won't be on the longest valid chain when all this is fixed." << curious to see if 0.5.whatever comes out on top at the end of this
ben_vulpes: r4ngn4phr0k
ben_vulpes: ph0rk
ben_vulpes: forkforkforkforkfork
ben_vulpes: FORK!
ben_vulpes: FORK?
ben_vulpes: FORK
ben_vulpes: punkman: have you tried my a47.sh?
ben_vulpes: phf: well hey like i said instructive
ben_vulpes: of the active users.
ben_vulpes: http://log.bitcoin-assets.com/?date=03-07-2015#1185122 << i grow curious about average hrs/user spent in eulora
ben_vulpes: asciilifeform: ^^
ben_vulpes: aha that's really nifty.
ben_vulpes: phf: (v. instructive among other good things)
ben_vulpes: asciilifeform: that cutblock c util was very instructive, ty
ben_vulpes: phf: ty for lisps
ben_vulpes: how does this thing even work
ben_vulpes: first link already 404d
ben_vulpes: muchas gracias for the hrdy link
ben_vulpes: leading any charge is risky and painful
ben_vulpes: asciilifeform: blockchain->sexprs or ragel parser
ben_vulpes: lol @ btc->sexprs, asciilifeform
ben_vulpes: http://blogs.scientificamerican.com/primate-diaries/raising-darwins-consciousness-an-interview-with-sarah-blaffer-hrdy-on-mother-nature/
ben_vulpes: i am *not* logged up
ben_vulpes: http://blogs.scientificamerican.com/primate-diaries/raising-darwins-consciousness-an-interview-with-sarah-blaffer-hrdy-/ << asciilifeform l0l 404!
ben_vulpes: http://log.bitcoin-assets.com/?date=03-07-2015#1184817 << paha goodness
ben_vulpes: http://log.bitcoin-assets.com/?date=02-07-2015#1184638 << asciilifeform, could i get a re-link to that piece on SIDS/implied infanticide?
ben_vulpes: more later, i have 2 hours of ferry ride coming up
ben_vulpes to breakfast with meatfriends
ben_vulpes: you'll spend less, they'll work less, and your systems will be vastly better for not having mongo in them
ben_vulpes: man you can get a sql user (not an expert, mind you, but someone who understands it has used it and can avoid common retardations) at half time for approximately half the cost of some hotshit "full stack developer" who thinks mongo's a good idea
ben_vulpes: http://log.bitcoin-assets.com/?date=02-07-2015#1184581 << and fucking how
ben_vulpes: and because none of them were designed for that in the first place because a) it's hard and b) fucking retards write nosql stores for hackernooz points the algebraic layer turns out to never actually work. or it locks everything up while running queries that a real db would plan handle like a boss
ben_vulpes: much like any c project eventually grows a miserable half-assed implementation of an eighth of common lisp any nosql project eventually tries to implement relational alggebra
ben_vulpes: otherwise you're going to start running the kind of braindamaged queries your 'nosql' layer support and then glomming it all together into something representing a query in application code
ben_vulpes: dude if it has a hint of structure it belongs in a relational db
ben_vulpes: (and even that can be handled by mother postgres at rather high efficiencies these days)
ben_vulpes: i've yet to see the real world problem that a nosql db was actually the right solution to that wasn't actually a cacheing/cdn problem
ben_vulpes: no man
ben_vulpes: recede
ben_vulpes: decimation: i'm finally seeing the tide receed from mongo's highwater
ben_vulpes: you can even derp the raw binary into pg if you're so inclined
ben_vulpes: if you're storing as the appropriate ints, floats, doubles, strings etc
ben_vulpes does not see the problem with hashing values queried directly out of the db