ben_vulpes: pete_dushenski: dude you gotta stop your blog from opening up links in new tabs
ben_vulpes: didja comment on their blorg?
ben_vulpes: ah cazalla yeah yeah
ben_vulpes: http://www.aaronsw.com/weblog/rewritingreddit << /me is amused at the "lisp/django" comparison
ben_vulpes: cazalla: what did you actually ask them? i eventually realized that the 32mb line is the nominal largest size of a p2p message.
ben_vulpes: 33MB lines when
ben_vulpes: quickly generate more logs for thickasthieves
ben_vulpes: ?
ben_vulpes: wasn't PeterL going to set up a new blogs.ba
ben_vulpes: neat! a dose of legitimacy.
ben_vulpes: not a bad notion at all
ben_vulpes: but fiatcorp calls at precisely this moment, and i must leave ye all for the meantime.
ben_vulpes: so i've cobbled together a testing stack that builds and boots this build as I mentioned last night. next things that i'd like to do with it is attach it to testnet; and stand up a server non-locally to run these builds.
ben_vulpes: testing bitcoin builds.
ben_vulpes: that latter's a tough one.
ben_vulpes: now im mulling what to publish
ben_vulpes: asciilifeform: i have one of those on me local machine
ben_vulpes: and i didn't see any good suggestions re "what is the output of a 'merge'?"
ben_vulpes: asciilifeform: is the mailing list up?
ben_vulpes: <jurov> ben_vulpes: what about bitcoin-enema.org ? f9beb4d9.org
ben_vulpes: truly a hanky story, but it's a step towards integration tests and what has one
ben_vulpes: so i've got a jenkins building this crazy stripped down build
ben_vulpes: a doctorow link in -assets?
ben_vulpes: markov chain
ben_vulpes: eligus is < 5%
ben_vulpes: "death of the preivous hard fork" meaning the actions that brought everyone onto the same chain?
ben_vulpes: mircea_popescu: so the pool operators really decide if the hard fork goes off, correct?
ben_vulpes: aight well fiat corp requires oiling before shuddering into motion in the morn. i'll continue this with anyone interested at a later point.
ben_vulpes mutters darkly
ben_vulpes: these crickets suggest that the chairs must make this decision.
ben_vulpes: fresh set of signed blobs in *.org/releases?
ben_vulpes: new "commit" in public repo?
ben_vulpes: q: what is the output of a "merge" in this scenario?
ben_vulpes: or political in the sense of 'forum'
ben_vulpes: is the goal (eg political) to find some poor usian schmuck to take on hearn et al and risk full audit of all things, stopping and frisking by every passing police officer?
ben_vulpes: choice for the technical role perhaps would be a better phrasing
ben_vulpes: trust the l2?
ben_vulpes: asciilifeform: but how theoretically would i know what to merge?
ben_vulpes: i've been staring at it and it's not unintelligble -- horrible, but not unintelligible -- but given things like obfuscated c competition i don't think i'm actually a good technical choice for the role
ben_vulpes: so i begin to wonder if i'm at all a good person to handle merges, given my lack of experience with cpp
ben_vulpes: so merges should only happen when k l m n o have already signed patch
ben_vulpes: mircea_popescu this is the thing you asked for in the first place: "sigs on lines"
ben_vulpes: and a record of patches signed by individuals
ben_vulpes: there's known state a
ben_vulpes: jurov's turdvendor's the canonical repository
ben_vulpes: lol no u
ben_vulpes: hang on a sec here
ben_vulpes: 32MB is not the steady-state line, it's just the largest sanctioned p2p msg
ben_vulpes: simple is beautiful
ben_vulpes: no stack to manage in that case; i'd prefer it if there are no obvious reasons to not.
ben_vulpes: forgive my derpitude but why not simply sign the patch and collect sigs?
ben_vulpes: mircea_popescu, asciilifeform: re sig stack is the implication that a signs patch, b signs patch and a.sig, c patch and b.sig...
ben_vulpes: where are the script kiddies draining the faucet...
ben_vulpes: i was just wondering about that!
ben_vulpes: should anyone *want* to endeedify their patch, they're welcome to.
ben_vulpes: no sense tangling things
ben_vulpes: punkman: a draft did, yeah. look for mod6's dpaste
ben_vulpes: pool administrators determine block size, correct?
ben_vulpes: i've a question about mining, for anyone who knows.
ben_vulpes: never imagined such.
ben_vulpes: asciilifeform: you weren't kidding about "glue and glass"
ben_vulpes: ick ick ick ick ick
ben_vulpes: lol
ben_vulpes: first showed up on wiki in march 2014
ben_vulpes: is -regtest not avail in 0.5.3?
ben_vulpes: 'download full bundle' link is broken
ben_vulpes: ;;ident punkman
ben_vulpes: ;;gpginfo punkman
ben_vulpes: ;;later tell dmzpkts tell me about ninjashogun's bet failure someday
ben_vulpes: ;;gettrust assbot ninjashogun
ben_vulpes: you're welcome kakobrekla
ben_vulpes: ;;rate muxne 1
ben_vulpes: hahaha
ben_vulpes: ;;gettrust assbot muxne
ben_vulpes: ;;gettrust assbot Vexual
ben_vulpes: !up Vexual
ben_vulpes: pah
ben_vulpes: which'd be too much wine?
ben_vulpes: aw shit i'm out of wine
ben_vulpes: no wait try this one http://www.xenosystems.net/the-cult-of-gnon/
ben_vulpes: although hey popehat that's a grand resource
ben_vulpes: mircea_popescu? skimming? will wonders never cease.
ben_vulpes: 2 links in; found mr mold
ben_vulpes: holy linkhole batman
ben_vulpes: mircea_popescu: shippments
ben_vulpes: ah sometimes probably
ben_vulpes: so sometimes the cock is 32mb long, but does the reference implementation accept those messages?
ben_vulpes: well this'd be the difference between a spec and an implementation, non?
ben_vulpes: ah
ben_vulpes: 100mn?
ben_vulpes: wait hm?
ben_vulpes: do enlighten me
ben_vulpes: "when i was your age, i got to work at 8, got off at 5, drank a beer, got on the train, went home and was at home. you poor fool answer emails lo unto 10pm"
ben_vulpes: your parents worked less than you and enjoyed their life more << i was just having this conversation with my father
ben_vulpes: oh god a giant trilema linking to other giant trilemas
ben_vulpes: "inside voice" is one of the more useful things to teach a dog: http://videos-f-16.ak.instagram.com/hphotos-ak-xfa1/10745249_1722322861325716_1685564917_n.mp4
ben_vulpes: thought it was just shitty
ben_vulpes: today i discovered that calibre ships with heuristic processing disabled
ben_vulpes: ah ha
ben_vulpes: blinked, remembered childhood german lessons
ben_vulpes: <asciilifeform> who hasn't seen a sign, marked, 'notausgang' - emergency exit << read as "not a us gang"
ben_vulpes: expend the set of people doing the thing and the copyfascists won't be able to keep up
ben_vulpes: <undata> I think it would be fantastic to have an appified (derped) way of downloading game of thrones << web browser torrent plugins exist
ben_vulpes: daw you boys are too sweet
ben_vulpes: Беркем аль Атоми << i don't even know how to find out more about this short of...learning to read russian.
ben_vulpes: interested to know where i went off the rails with that one
ben_vulpes: http://cascadianhacker.com/blog/2014/10/25_notes-on-increasing-the-maximum-bitcoin-block-size-or-why-it-aint-happenin.html
ben_vulpes: mircea_popescu: do messages of less than 32 MB transmit regularly? are you aware of a discernable phase boundary for transmission reliability?
ben_vulpes: ty mircea_popescu
ben_vulpes: how would i get the size of an arbitrary block?
ben_vulpes: (just trolling - all the paupers have to)
ben_vulpes: ;;later tell princesnell https://bitcoinfoundation.org/2014/10/blocksize-economics/ << what, you're collaborating with the empire nao?
ben_vulpes: which has got to be the most orwellianly named product out there
ben_vulpes: decimation: i used it for time tracking before we started using harvest
ben_vulpes: decimation: why do you ask?
ben_vulpes: as in p2p messages exceed 32mb in practice?
ben_vulpes: side note about the 32mb number: andresen claims that as the largest message that can be sent in a single bitcoin p2p message.
ben_vulpes: !
ben_vulpes: fairly frequently, yes.
ben_vulpes: integration with grep, ag, and the kill-ring visualization are pretty fantastic.
ben_vulpes: decimation: http://tuhdo.github.io/helm-projectile.html
ben_vulpes: decimation: http://tuhdo.github.io/helm-intro.html
ben_vulpes: hang on a sec
ben_vulpes: (mircea_popescu: https://github.com/bitcoin/bitcoin/pull/4481/files#diff-c865a8939105e6350a50af02766291b7R605 << the first one, de-typo'd)
ben_vulpes: fuzzy completion in all of the places in which one'd want it?
ben_vulpes: decimation: are you familiar with ido?
ben_vulpes: mircea_popescu: terminal kill ring, incomplete backwards-kill, os paste holder
ben_vulpes: i finally got helm dialed in (and oh my god, i didn't know that emacs could get that much better
ben_vulpes: but it's on the roadmap for 2015
ben_vulpes: i've yet to set it up myself
ben_vulpes: decimation: konqueror
ben_vulpes: https://github.com/bitcoin/bitcoin/pull/4481/files#diff-c865a8939105e6350a50af02766291b7R980
ben_vulpes: pardon sir, a typo
ben_vulpes: prhttps?
ben_vulpes: prhttps://github.com/bitcoin/bitcoin/pull/4481/files#diff-c865a8939105e6350a50af02766291b7R980 << ah satoshi save me
ben_vulpes: can't run with a wallet in pruned mode?
ben_vulpes: prhttps://github.com/bitcoin/bitcoin/pull/4481/files#diff-c865a8939105e6350a50af02766291b7R605
ben_vulpes: what is the actual serious problem?
ben_vulpes: this "pruned blockchain" notion sounds dangerous.
ben_vulpes: cazalla: did you hear back from Conformal about the machines they used to come to their 32MB steady-state conclusion?
ben_vulpes: no venture investment
ben_vulpes: bad search as a service
ben_vulpes: o.O
ben_vulpes: !s bitcoin dark secret
ben_vulpes: undata: i'm using debian.
ben_vulpes: debian and gentoo seem to be the choices.
ben_vulpes: <decimation> ben_vulpes: did you manage to compile your package on osx? << not even trying. i set up a virtualized debian toolchain.
ben_vulpes: vermin supreme!
ben_vulpes: certainly.
ben_vulpes: mailing list that accepts messages from assbot's l2
ben_vulpes: but tis but a guess and that guess from me, and discounts should be applied heavily.
ben_vulpes: few things are certain even to those capable of reasoning about them. i must fumble in the dark making guesses. my guess though, is that some parts of it work.
ben_vulpes: if it does what it says on the tin, i find it a vastly more palatable meal than say a dollar
ben_vulpes: what a miserable, beautiful turd.
ben_vulpes: what a turd
ben_vulpes: it's at least an example of the desired process.
ben_vulpes: does UPNP removal count as a cosmetic change?
ben_vulpes: best to do it correctly, though. and binaries are not my concern - source is.
ben_vulpes: did indeed.
ben_vulpes: asciilifeform: http://cascadianhacker.com/rm_rf_upnp.tar.gz << i believe this excises all upnp mentions. my build hops on the network and downloads blocks.
ben_vulpes: watch that turn out to be an aws maxi-sized VPS
ben_vulpes: myeah.
ben_vulpes: cazalla: ^^
ben_vulpes: article.
ben_vulpes: what are the stats of this "one machine"?
ben_vulpes: right right
ben_vulpes: i'd like to have a thing that built a patch; booted the resulting artifact on testnet, mined some TN coins, sent them to itself, etc
ben_vulpes shrugs
ben_vulpes: surely there's more rigor possible than this.
ben_vulpes: i build the thing, and then boot it, and if getblockcount increments under my eye - it passes?
ben_vulpes: this is kind of terrifying.
ben_vulpes: test_bitcoin.cpp
ben_vulpes: oh lol
ben_vulpes: would like to run tests, write tests, etc
ben_vulpes: i have zero familiarity with the c ecosystem
ben_vulpes: the test-bitcoin line in makefile.unix - is that where i should look for running tests?
ben_vulpes: you're the literate one...
ben_vulpes: whence the k tho
ben_vulpes: yes yes
ben_vulpes: kistor?
ben_vulpes: ah
ben_vulpes: ag
ben_vulpes: asciilifeform: does "tree" entail "contrib" as well?
ben_vulpes: "dnsseed.bitcoin.dashjr.org",
ben_vulpes: the same.
ben_vulpes: wrong seed.
ben_vulpes: dashjr...
ben_vulpes: asciilifeform: to digress, what's the rationale behind keeping makefile.linux-mingw?
ben_vulpes: responses to patch thread with sigs?
ben_vulpes: <asciilifeform> jurov: also at some point we ought to have people sign off on others' patches, once they read << would a new tarball with sig attached suffice?
ben_vulpes: wherever's clever.
ben_vulpes: doesn't matter.
ben_vulpes: if only mircea_popescu were still giving away domains...
ben_vulpes: perhaps too obscure
ben_vulpes: the network magic bytes for mainnet
ben_vulpes: jurov: i'd love to see it at f9beb4d9.org
ben_vulpes: ah.
ben_vulpes: asciilifeform: http://cascadianhacker.com/rm_rf_upnp.tar.gz << am i doing it correctly?
ben_vulpes: nubbins`: too intense?
ben_vulpes: qrcode :D
ben_vulpes: undata: few automated services need to send btc.
ben_vulpes: build time down to a minute.
ben_vulpes: also, not really in the scope.
ben_vulpes: talk to the binary running on the machine.
ben_vulpes: undata: 'twould be nice.
ben_vulpes: i doubt it, but who can ever tell.
ben_vulpes: turd_vendor
ben_vulpes: mkay.
ben_vulpes: asciilifeform: tooling question: when working on the actual c files, should i be working in a parallel directory and then diff -uNr original_dir my_dir > patch.diff?
ben_vulpes: 'competence'
ben_vulpes: am now squarely out of competence zone
ben_vulpes: asciilifeform: next step is to coerce 'git' into pooping out sane patch
ben_vulpes: impostor
ben_vulpes: !up nubbins`
ben_vulpes: asciilifeform: builds, runs.
ben_vulpes: asciilifeform: spitoon, rather.
ben_vulpes: i and boys slave in golden cage, fabbing golden toilets
ben_vulpes: <asciilifeform> decadent rich << describes clients and their target customers quite well
ben_vulpes: asciilifeform: mocking paupers :(
ben_vulpes: macos
ben_vulpes: turds in turds on turds
ben_vulpes: asciilifeform: i'm running it in a debian vm
ben_vulpes: that's a narrow hair from "just one more bag - it'll be fine."
ben_vulpes: mircea_popescu: "let me fly the plane! i've got like 20 sim hours!"
ben_vulpes: wrote my own patch ripping out upnp dependency, build is now taking forever.
ben_vulpes: asciilifeform: building.
ben_vulpes: NO HTML
ben_vulpes: NO
ben_vulpes: Adlai: you're welcome.
ben_vulpes: <Mikayla> I've had to walk to buy electricity at night once << bwaaat
ben_vulpes: i was very tired when i wrote that.
ben_vulpes: in retrospect that should be "ether distribution"
ben_vulpes: <Adlai> but umm yeah... you're buying private keys. this is silly. << http://cascadianhacker.com/blog/2014/10/22_technical-flaws-in-early-ether-wallet-implementations.html
ben_vulpes: asciilifeform: sandworm or god emperor?
ben_vulpes: ;;google fuck you i'm a dragon
ben_vulpes: anyways that's it for me tonight
ben_vulpes: no comment necessary, simply sharing lulz.
ben_vulpes: Bugpowder: on the topic of bezzlenomics, i'm amused that you have a small grant, lab, equipment and...porsche.
ben_vulpes: bitcoin anything on anything one owns - big advertisement for rectothermal cryptanalysts
ben_vulpes: b) "lol plate ams left justified cuz i generate keys wasted"
ben_vulpes: a) "hai plz foar ams to rob me"
ben_vulpes: <Bugpowder> left justified plate. FML << typical bitcoiner
ben_vulpes: haha oh man ripped up one side and down t' other
ben_vulpes: <PinkPosixPXE> re QR codes and exposing privkeys to the atmosphere: http://www.bloomberg.com/video/miller-s-lesson-guard-your-bitcoin-qr-code-1y5Uj8foQu~3Gn_qKclleQ.html << "never show anyone your public key" ya mhm bloomberg killing it again and again