ben_vulpes: also, single-file vpatches drives the system towards whole sourcetree hashing, otherwise they'll definitionally never depend on one another
ben_vulpes: phf: this exposes another problem: in ideal vtronics it is an illegal operation to press to multiple leaves at the same tree level, which is the only way to have a codebase against which to create a makefiles-type patch that ties multiple patches together
ben_vulpes: aha k
ben_vulpes: phf: which vpatch does this show up in?
ben_vulpes: this still leaves me in the pickle of producing a vpatch from a press to a that won't actually descend linearly from a without touching a file, and adding "this line necessary to ensure this vpatch descends from a and not genesis"
ben_vulpes: so far the solutions i see are a) mircea_popescu's "what tree, all patches must descend linearly or be reground into linearity" 2) allow for pressing heads that do not touch the same files
ben_vulpes: it may be that tracking hashes at the file level isn't the right thing, because with vdiff as implemented i can trivially generate a vpatch b while working from a press of a that nevertheless still only depends on genesis if a leaves files untouched and b touches those untouched files only
ben_vulpes: #define true false
ben_vulpes: where's your holiday spirit, diana_coman
ben_vulpes: borstal: that's it?
ben_vulpes: it's still 2017, borstal, what do you have to show for how you've lived your life?
ben_vulpes: !!up borstal
ben_vulpes: !!up seefelder
ben_vulpes: mircea_popescu: aye aye
ben_vulpes: and in other profitable mining strategies: https://www.nytimes.com/2017/12/25/business/energy-environment/germany-electricity-negative-prices.html
ben_vulpes: http://btcbase.org/log/2017-12-26#1758614 << consider a genesis, a and b patchset where a and b don't touch the same files. if i press to b, write a c that descends from b, it will not have a as an antecedent. when you say "modify the filebase into the shape that you want it to be", do you mean include the changes of a in the c patch?
ben_vulpes: !!up BigTexasBingo
ben_vulpes: the specifics of this case is that increase_aggression_levels touches *only* net.cpp and excise_hash_truncations touches a whole lotta stuff but *not* net.cpp
ben_vulpes: that don't touch the same file
ben_vulpes: i baked the vpatch i'm working on by pressing to excise_hash_truncation which only works accidentally, as v.pl presses both leaves at that level (first increase_aggression_levels and then excise_hash_truncation); but i don't see a route to producing a vpatch stitching together excise_hash_truncation and increase_aggression_levels without doing something that v doesn't support like pressing multiple heads
ben_vulpes: asciilifeform, mod6, mircea_popescu: because an ideal v wouldn't apply both increase_aggression_levels and excise_hash_truncation when pressing excise_hash_truncation, how do i make another vpatch depend on both of those without needlessly touching a file changed in excise_hash_truncations to make increase_aggression_levels depend on it or vice versa?
ben_vulpes: https://www.bloomberg.com/view/articles/2017-12-22/business-consultant-submits-perfect-bill
ben_vulpes: could have agreed to pay it, so it must not have been disclosed. Even if it actually was."
ben_vulpes: "The SEC, on the other hand, thinks that the accelerated monitoring fees themselves were dumb and bad. It is not wrong, exactly, about that. But dumb and bad fees are not, in general, violations of the securities laws, and so the SEC has to pretend that the dumb and bad fees were also not disclosed. It is sort of a charming picture of the investment industry: If a fee is dumb and bad enough, then no investor
ben_vulpes: and in bbc news today http://currentnewsinnigeria.com/2017/12/shocking-porn-video-showing-man-woman-having-sex-mistakenly-displayed-in-church-during-church-service-photo/
ben_vulpes: join #/join ?
ben_vulpes: !!down lollig400
ben_vulpes: !!up lollig400
ben_vulpes: oho i think i see why the rebroadcaster appeared to fail completely, nobody likes trb dust
ben_vulpes: will post the transaction dumper later, after i tinker with it a bit more.
ben_vulpes: http://btcbase.org/log/2017-12-21#1755738 << i wrote both a "rebroadcasttransaction" and a "dumprawtx"; the former categorically did not work, the latter...at least produces raw transactions on disk.
ben_vulpes: !!reputation MTW
ben_vulpes: geeeeeet in there!
ben_vulpes: all worlds outside #trilema are the alt-world
ben_vulpes: indeed!
ben_vulpes: and in other cribbings from trilema: "there's no price signal omgwtfbbq!" https://davidgerard.co.uk/blockchain/2017/12/17/why-you-cant-cash-out-pt-1-why-bitcoins-price-is-largely-fictional/
ben_vulpes: phf: ty!
ben_vulpes: asciilifeform mod6 phf mircea_popescu trinque and phriendz: http://therealbitcoin.org/ml/btc-dev/2017-December/000283.html
ben_vulpes: sweet! thanks phf
ben_vulpes: in other random lols: 2017-12-25_02:27:44.00324 version message: version 70013, blocks=0
ben_vulpes: mircea_popescu: am looking more for "open throttle to max airflow" knob than holographic stickers to increase hp
ben_vulpes: anyways, my node is now either fourteen or fifteen minutes behind bc.i depending on how their javascript feels, so perhaps there's nothing to this aggression after all, sorry to disappoint BigTexasBingo
ben_vulpes: i imagine there's some "isomorphic backend rendering" node black magic horseshit going on behind the scenes
ben_vulpes: yeah, and this is true of all their listed blocks
ben_vulpes: danielpbarron: first the page renders with 500918: 12, then five seconds later 500918 now apparently has an age of 13 minutes
ben_vulpes: the magic of javascript! you can decide what world you live in!
ben_vulpes: wowee, when i reload blockchain.info first it shows one number for how long a block's been advertised and then shortly thereafter, another number indicating they've known about it for longer than they said at first!
ben_vulpes: noches, btb
ben_vulpes: !!up BigTexasBingo
ben_vulpes: i'll have to look into how block height is advertised but that makes sense mircea_popescu
ben_vulpes: shinohai: howabout a timeout knob? every <configurable> minutes after the last block, pushgetblocks to all peers?
ben_vulpes: mircea_popescu: that could in theory be once and never after for long-running and stable connections
ben_vulpes: is there an argument to be made against asking peers for new blocks every time TRB loops through the peerlist? too resource-intensive?
ben_vulpes: c block means a.b.c.d right?
ben_vulpes: and eyy, just caught a block before blockchain.info
ben_vulpes toasts trinque
ben_vulpes: !!up KutmasteR merry kutmas
ben_vulpes: facsimilie*
ben_vulpes: lol what kind of unholy fascimilie is that
ben_vulpes: > cannapeg
ben_vulpes: shinohai: lol pics?
ben_vulpes: http://p.bvulpes.com/pastes/2tKj7/?raw=true current vpatch for the curious, will post to ml after letting it run for a while
ben_vulpes: there's ~no way that the timeout requestment has fired yet
ben_vulpes: pflol well after excising max_outbound_connections and the one-connection-per-block connection count now at 114 and node very quickly got back up to date
ben_vulpes: do i look like i'm kidding?
ben_vulpes: let's try again: i misnamed the seal for the truncation patch, must have "ben_vulpes" in the last period-delimited field of the seal name instead of "ben_vules"
ben_vulpes: otherwise v.pl won't recognize it as a seal.
ben_vulpes: while i wait for the mailing list to process my latest note, please note that the sig attached in http://btcbase.org/log/2017-12-24#1758230 needs renaming to `ben_vulpes_excise_hash_truncation.vpatch.ben_vulpes.sig'
ben_vulpes: also it is *snowing* on *christmas eve* in the northern suburbs of the socialist paradise
ben_vulpes: meanwhile, i (sadly) understand http://btcbase.org/log/2017-12-24#1758272 now
ben_vulpes: aight
ben_vulpes: god sent him a sign, what's he going to do with it.
ben_vulpes: http://p.bvulpes.com/pastes/JWdTT/?raw=true for the curious, dear gregory pery do call in, our listeners are dying to meet you
ben_vulpes: ftr, i dun expect a response
ben_vulpes: but judging from how the biofilm uses symbols instead of thinking i rather expect that the protonmail address is read
ben_vulpes: mircea_popescu: i actually already emailed him
ben_vulpes: my feelings!
ben_vulpes: hurtful!
ben_vulpes: but in particular i hate cpp
ben_vulpes: i hate everything
ben_vulpes: no updating and no coming!
ben_vulpes whimpers
ben_vulpes: does it? does it really? what the fuck does work even mean here.
ben_vulpes: that bitmashing against the ip makes my head hurt.
ben_vulpes: also what on earth is http://btc.yt/lxr/satoshi/source/src/net.cpp?v=makefiles#1000
ben_vulpes: well the question rattling around me braincase is ~"does this help or hinder weaponized TRB?"
ben_vulpes: gotcha
ben_vulpes: adcockery!
ben_vulpes: right right.
ben_vulpes: ah and when its ip gets passed around the network, it simply shits the whole world up.
ben_vulpes suffering from a confusion of ideas
ben_vulpes: why do the NAT node connections threaten to take down realnodes?
ben_vulpes: mircea_popescu: yeah i pulled the trigger on that excision along with the hash truncation, see the ml
ben_vulpes: i don't quite see the connection between NATed nodes and this max outbound connections constraint, could you elaborate?
ben_vulpes: http://btc.yt/lxr/satoshi/source/src/net.cpp?v=makefiles#0016 << hey here's an interesting
ben_vulpes: how many power rangers did you kill today...
ben_vulpes: mod6 asciilifeform et al: http://therealbitcoin.org/ml/btc-dev/2017-December/000282.html
ben_vulpes running truncation patch, will get back in the saddle after misc duties of parenting while impoverished
ben_vulpes: and they need a next gen authentication framework to fix it...
ben_vulpes: absurdly common
ben_vulpes: https://medium.com/bread-and-circuses/how-i-got-paid-0-from-the-uber-security-bug-bounty-aa9646aa103f and in responsible disclosurabilia
ben_vulpes: mhm
ben_vulpes: what port are you connecting on?
ben_vulpes: and only from aws ips?
ben_vulpes: lolrly??
ben_vulpes: traveling through the suburban wastelands yesterday, i tried a 'starbucks' croissant for lols, thinking to myself, 'imagine if they can screw up the croissant'. and lo, it was terrible. no flake, all soft spongiform inside.
ben_vulpes: ah, makefiles. suresure.
ben_vulpes: http://btc.yt/lxr/satoshi/source/src/db.cpp#0837 << any reason for this to not come out with the truncation patch?
ben_vulpes: salud.
ben_vulpes: and no, opinions don't exist here if they don't come from *a person*, which is predicated on an identity.
ben_vulpes: Hssgh5337k: you could at least mention these skills; otherwise it reeks of "i'm a magical pony and YOU DON'T UNDERSTAAAAND"
ben_vulpes: ;)
ben_vulpes: who are you anyways
ben_vulpes: oh right
ben_vulpes: come 2020 if not sooner, it'll be "and i beg your consideration".
ben_vulpes: and to quote BigTexasBingo, the time for showing up and derping around without saying "i am so and so, and should be considered for inclusion in the forum for reasons of x y and z" was in 2013, not the tail end of 2017.
ben_vulpes: absent identity, one is naught.
ben_vulpes: and who're you, Hssgh5337k ?
ben_vulpes: !!up Hssgh5337k
ben_vulpes: a pies, ideally
ben_vulpes: ah si
ben_vulpes: no party in the streets?
ben_vulpes: como esto possible?
ben_vulpes: mas tranquilo?
ben_vulpes: hola jefe
ben_vulpes: !!up BigTexasBingo
ben_vulpes: (hash and height, i mean)
ben_vulpes: lol that's right it comes out of SetBestChain
ben_vulpes: right right
ben_vulpes: heh and what was its height and hash
ben_vulpes: i have another kiestered that i may as well unload at the same time, hash untrunculation
ben_vulpes: yeah definitely
ben_vulpes: asciilifeform: the same thought occurred to me
ben_vulpes: node was booted with that yes
ben_vulpes: this one block took me from 813 to 814
ben_vulpes: asciilifeform: one thing i do with logbot is to use postgres as a queue so that a background worker can do all of the thinking and crashing without thrashing the irc connection
ben_vulpes: anyways i must have an extra-thick layer of prb, as my node has found precisely one block in the past three hours
ben_vulpes: sorry, asciilifeform. i was focused on the logbot part, forgot about the ircbot and to update documentation.
ben_vulpes: sharp eyes, asciilifeform
ben_vulpes: fair warning, it has a miserable, lisprepl ui
ben_vulpes: shall i dig mine out?
ben_vulpes: vtron != vdiff mircea_popescu
ben_vulpes: trinque: hah cool
ben_vulpes: hm
ben_vulpes: tangentially relatedly, i'm not seeing much benefit from this aggressive sync mode
ben_vulpes: myeah, as i said "in light of", mostly unearthing for target practice.
ben_vulpes: also re-found http://40.media.tumblr.com/3ea4c6cfd1af432bba0675b8bde21056/tumblr_n74hilKQPB1qzuheco1_1280.jpg
ben_vulpes still rereading whole thread in light of the past few days happenings
ben_vulpes: in other topical historical items: http://btcbase.org/log/2015-11-14#1323384
ben_vulpes: i think i just tripped over the multiple-leaves thing as well, had asciilifeform's wires in my patchset
ben_vulpes: you know, when getinfo got around to returning
ben_vulpes: > 749
ben_vulpes: just caught 2 more; looks like it might be on a verification tear now
ben_vulpes: will probably use asciilifeform's aggressive patch, as my logs are full of 70000-series nodes advertising sexily high tips
ben_vulpes: this one is so very persistently stuck at 500756
ben_vulpes: "A federal judge declared a mistrial wednesay in the riminal conspiracy case against rancher Cliven Bundy and three other defendants, saying government laywers suppressed key evidence..." https://www.washingtonpost.com/national/judge-declares-mistrial-in-case-against-rancher-cliven-bundy-sons-and-militiaman/2017/12/20/49d91c24-e5c8-11e7-a65d-1ac0fd7f097e_story.html
ben_vulpes: phf: well i'd like to get something out of trb that i can dump into a txrelayulator
ben_vulpes: eh, insufficiently explicit
ben_vulpes: s/could be/is/
ben_vulpes: sure, could be reasonable to dump to <txid>.bin in my mind as well
ben_vulpes: and cwallettx has the kooky IMPLEMENT_SERIALIZE so it should be possible to hex to stdout through the rpc machinery?
ben_vulpes: phf: i was thinking something in this area http://btcbase.org/patches/makefiles/tree/bitcoin/src/bitcoinrpc.cpp#L1320
ben_vulpes: even pantsuits know: https://www.theatlantic.com/magazine/archive/2017/09/has-the-smartphone-destroyed-a-generation/534198/
ben_vulpes: phf: the latter
ben_vulpes: aside from dumping the mempool and parsing each?
ben_vulpes: unrelatedly, does anyone know how to beat a trb into coughing up the actual raw transaction it sent?
ben_vulpes: actually just dug out some photos from that era, oh gracious me. macs with cameras were all the rage and boy howdy did we have fun taking photos of ourselves misbehaving.
ben_vulpes: had display on the outside, could read texts without opening the thing. had google maps; internet over cell; a marvelous little device. great camera for the time as well.
ben_vulpes: phf: total transformerphone
ben_vulpes: a) don't live there or care too much about barista fashion anymore b) already lead that charge by toting the mp01 for a few months c) wake me up when "i don't have facebook" is actually popular
ben_vulpes: https://www.ebay.com/itm/NOKIA-N90-Type-RM-42-Smartphone-Cellular-Collectible-GSM-Mobile-N-Series-Vintage/132438876949?epid=100040237&hash=item1ed5f8e315:g:MvYAAOSwDKtY2ZB1 << shit was my jam in 06
ben_vulpes: phf: you know me so well
ben_vulpes: anyways cblgh logs are in channel title, if you're going to not wash out at least register a gpg key with deedbot
ben_vulpes: not you lol
ben_vulpes: ahaha when did you show up
ben_vulpes: i have developed an allergy to bending myself to fit my tools over the last four years; ios is one of the last bits of sand in me gears
ben_vulpes: lol hah
ben_vulpes: pretty tragic that one even has the basis to ask 'how bad is the t9', given how well it worked two decades ago.
ben_vulpes: you're happier hammering each numpad up to three times for a single letter?
ben_vulpes: asciilifeform: hey, t9 implementations suck now too. no auto-updating dictionary, statistic-based wordguessing...
ben_vulpes: how's the t9?
ben_vulpes: ah looks like a classic
ben_vulpes: phf: rocking the 'mp01' or what
ben_vulpes: probably tastes great with a dash of "selectively run js load from google.com, facebook.com after everything else because trackers are js dogs"
ben_vulpes: energy efficient, dontchaknow!
ben_vulpes: let's just continue with the apple idiocy: "try the new safari! fast, energy efficient, and with a beautiful new design."
ben_vulpes: i guess this is new as of the lifted ban on interpreters and compilers?
ben_vulpes: phf: oh that's nifty
ben_vulpes: or 'IT will want to know how to upgrade users devices without revoking every key and leaving accounts 'unsecured' during the TOTP rotation"
ben_vulpes: im astonished this idiocy made it past the enterprise sales people; 'IT will want to know how to back these codes up'
ben_vulpes: here i was, thinking that a redhat product would have features like 'backup'
ben_vulpes: asciilifeform: yr defectively steeped in security theater
ben_vulpes: in other top notch lolz, the redhat "totp" ios "app" does not provide for backing up the shared seeds.
ben_vulpes: the real fun is in asking "what word do you want me to use instead?" and then using it in such a way that all the partizans wince, knowing that word means The Bad Thing now.
ben_vulpes: "humans can't be defective!" "well what do you call it when they're missing a chromosome, eh?"
ben_vulpes: it's wildly entertaining watching people thrash in their own contradictions
ben_vulpes: not even use, but locked up trying to find
ben_vulpes: a few short seconds later the same person practically pulled a 'halt and catch fire' when attempting to use a word that doesn't mean broken to describe f. ex. chromosomal abnormalities
ben_vulpes: just my dinner table
ben_vulpes: i had to laugh last night; someone at the table wanted to stake out the position that "people with downs syndrome aren't defective. you can't have defective humans!"
ben_vulpes: shinohai: megalol at insider trading of altcoins
ben_vulpes: if an email player, why not a music reader?!
ben_vulpes: how many lines of code did you kill today!
ben_vulpes: hey, life and wife and kids and job and commute and and and i can readily see how difficult it'd be
ben_vulpes: including (omg!!!1) keyword search
ben_vulpes: rolling out radical piles of features at okcupid
ben_vulpes: how was that established again
ben_vulpes: did we?
ben_vulpes: asciilifeform: 'magic trick' vs 'as yet unbroken cipher'
ben_vulpes: still not convinced that no hanky panky was involved
ben_vulpes: that fuckin thing
ben_vulpes: although perhaps that is the only thing that will eventually differentiate the trilema fiatists products
ben_vulpes: asciilifeform: i am very curious in how you figure initial distribution might work
ben_vulpes: ohey have we finally arrived at the solution of each laird maintaining their own premined coin?
ben_vulpes: https://www.washingtontimes.com/news/2017/dec/18/report-obama-protected-hezbollah-drug-ring-to-avoi/
ben_vulpes: she would literally rather dance for tips
ben_vulpes: what a fuckin thing.
ben_vulpes: holy fuckadoodle, imagine getting paid a bitcent an hour to do your six months
ben_vulpes: mircea_popescu: oh i understand this, i also understand how fist fits in cunt doesn't mean i'm not entertained from time to time with the concrete item
ben_vulpes: doing anything but that which needs doing.
ben_vulpes: dude this is epic, girl would rather talk about calendar offsets than earn a bitcent an hour reading the log
ben_vulpes: sofiababy: what the hell is wrong with you
ben_vulpes: dude a bitcent an hour
ben_vulpes: for five seconds, an interesting thing happened on mfc
ben_vulpes: no reading is happening
ben_vulpes: who cares what they think?
ben_vulpes: i thought it was cute!
ben_vulpes: gods bless, his webpage loads in half a second
ben_vulpes: and now for something completely different: http://archive.is/IEa6u "I have always been fascinated, and a little troubled, by the concept of paper money, or fiat currency. If I think about it too long it makes my head hurt and I have an urge to sell all of my tech stocks and buy gold."
ben_vulpes: http://archive.is/p526V << certain elements of the pravda are funny; the classic socialistoid "assuming the sale" in "The truth has been rendered here irrelevant" in regards to the /defamation case/, also the hilarious verdict of ~"you'd have to be /uniquely stupid/ to not understand that you're a public figure by virtue of just fucking look at yourself"
ben_vulpes: well and being a pissoir for the webatlarge
ben_vulpes: asciilifeform: macware abounds, none of it is being used for anything other than entertainment anymore
ben_vulpes: phf: nah not particularly interesting to me, i got out of that gox early q2 this year, but sfyl
ben_vulpes bbl, a deserving lady has a christmas movie i'm not grinching about for once
ben_vulpes: american democracy is a miserable thing, demanding that there be one boss (the state) and all subservient to it without ever acknowledging their subservience.
ben_vulpes: when i ran a small coeterie of staff the steel spine of our success was the chain of command from whence sense and marching orders came, and everyone's utterly clear understanding of where they stood
ben_vulpes: mircea_popescu: never seen it
ben_vulpes: such a sad thing, the rejection of hierarchy.
ben_vulpes: now if only there were anything to talk about over beer but gay marriage
ben_vulpes: inneresting
ben_vulpes: in other possibly stale lols, heathen wallet denominates in millishitcoinz
ben_vulpes: ty
ben_vulpes: so 'in out' means that data can be read from the param and will also be written into, whereas 'out' means that data will only be written to the param in the procedure?
ben_vulpes: okay i'll look into that.
ben_vulpes: hm
ben_vulpes: ah because you still pass outparams into a function call
ben_vulpes: asciilifeform: ^^
ben_vulpes: anyways, way the heck upstack, `FZ_Clear` 'sets a given FZ to zero' but i only see an outparam; is this not more of a constructor than zero-er?
ben_vulpes: large thermal mass, engineering time spent to ensure complete combustion, sometimes a long horizontal chimney too?