ben_vulpes: it /should/ be 'parsimoniously'
ben_vulpes: BingoBoingo: 'parsimoniously'
ben_vulpes: clang
ben_vulpes: sorry
ben_vulpes: er yes
ben_vulpes: works like a chaaaarm
ben_vulpes: mod6: phf dumped a patch in the logs for compiling under gcc
ben_vulpes: i have no idea if this is fast or slow
ben_vulpes: 5s after adding a printf to shiva.cpp
ben_vulpes: i have no idea if this is an abnormally long or short time
ben_vulpes: on a 2.66 GHz IC2Duo.
ben_vulpes: http://log.bitcoin-assets.com/?date=02-03-2016#1419829 << with phf's patch (are you going to post that to the ML or shall i?), my post-clean compile takes 1m 16s
ben_vulpes: mod6: this is 'rotor_bitcoin_only.sh' in the rotor tarball
ben_vulpes: http://log.bitcoin-assets.com/?date=02-03-2016#1419758 << very much i do
ben_vulpes: waiwut how does it make economic sense to not release blocks?
ben_vulpes: !s zoolag
ben_vulpes: !up Anduck
ben_vulpes: and what is 'cdb' mircea_popescu ?
ben_vulpes: wait how is phyctor going to be +ev?
ben_vulpes: ( jurov i chuckled )
ben_vulpes: fractally bad code
ben_vulpes: i'd like to see that list!
ben_vulpes: the hundred dollar store is pretty funny
ben_vulpes: ofc
ben_vulpes: probably more crowded than anything mircea_popescu engages in willingly, and i don't even like it.
ben_vulpes: some real horrific tiny house gypsy shit: 2 adults, 1 infant and 80lbs of ferocious lovedog in a queen bed
ben_vulpes: stirs a mite, gets fed, goes back to sleep.
ben_vulpes: well he sleeps through the night, let's start there
ben_vulpes: putting the pressure on to get him into his bassinet more regularly
ben_vulpes: mhm!
ben_vulpes: must be that dogecoin guy again
ben_vulpes: i wonder how the conversation drifted from parenting to shillcoins
ben_vulpes: http://log.bitcoin-assets.com/?date=24-12-2015#1351555 << four months in, beginning to reheheheally feel this
ben_vulpes: MORE FROWNING
ben_vulpes: starting to give a shit about his dad yet?
ben_vulpes: pardon, i misremembered.
ben_vulpes: your first was a male?
ben_vulpes: there's only so much damage the little fuckling can do in 485 ft2
ben_vulpes: cazalla: rolled over the other day!
ben_vulpes: two dowries!
ben_vulpes: that's two!
ben_vulpes: b/g?
ben_vulpes: how many weeks along?
ben_vulpes: anyways, how's the second cooking, cazalla ?
ben_vulpes: why so butthurt
ben_vulpes: well i'm just having a conversation with an old friend i haven't seen in a few weeks, but thanks for getting involved!
ben_vulpes: i'll not talk to any 'staff-emeritus' in pm
ben_vulpes: !up SuchWow if you have complaints to render feel free to do so here
ben_vulpes: well hi!
ben_vulpes: ah and assbot yelled at me too
ben_vulpes: !down SuchWow
ben_vulpes: !up SuchWow
ben_vulpes: !down cazalla
ben_vulpes: can we down each other?
ben_vulpes: yeah, i saw the second go through, but i don't think there's a guarantee that *you* did the second one.
ben_vulpes: hm actually i upped you so how would i know
ben_vulpes: briefly considered 'cock in hand'
ben_vulpes: heh
ben_vulpes: cazalla: good to see you key in hand
ben_vulpes: punkman: like 10ms? 100ms? 1s?
ben_vulpes: hey boss
ben_vulpes: !up cazalla
ben_vulpes: i am also curious to hear about how long the bitcoind recompile is in your various workflows, asciilifeform, phf, mod6, punkman, jurov
ben_vulpes: http://log.bitcoin-assets.com/?date=03-02-2016#1395250 << asciilifeform what was the actual trigger for the blackhole? requesting a specific transaction?
ben_vulpes: not interested in btc politics botneko-chan ? just in it for the ddos?
ben_vulpes: botneko-chan: ^^
ben_vulpes: what do the Core people think about increasing the block size?
ben_vulpes: botneko-chan: what is Core?
ben_vulpes: phf, nevermind, i'm a classic core derp
ben_vulpes: there's no actual panic, botneko-chan. there are a zillion for-hire-for-pennies social media accounts supporting some nsa plants attempts to matter with kindergarten grade psyops.
ben_vulpes: wtf this was working yesterday
ben_vulpes: running the /exact same/ bitcoind command runs something that i can telnet into and scream lisp at
ben_vulpes: while last night the swank flags worked just handily, tonight, passing the swank flag to a booting bitcoind results in an error, "too short", from scheme.cpp
ben_vulpes: phf: here's a stumper
ben_vulpes: HOOOOOOOOOO
ben_vulpes: there's one for the dustbin.
ben_vulpes: flycheck just deleted the contents of an entire buffer
ben_vulpes: welp
ben_vulpes: asciilifeform: and the reason you picked tinyscheme over say ecl is...footprint? dreppers in ecl?
ben_vulpes: jurov: highly nifty
ben_vulpes: because the counterparty in this conversation is not thinking of gossipd as a device but a proggy that runs on a computer.
ben_vulpes: "pff line speed. you still need to get the buffered packets from the kernel into userspace, and that's an abstraction you'll have a hard time getting around."
ben_vulpes: "yeah man! big challenge though is to get it to operate at line speed."
ben_vulpes: asciilifeform: what's your cad poison of choice?
ben_vulpes: mwell now that you ask...
ben_vulpes: "because lol what we're going to fab our own chips?"
ben_vulpes: got someone bought in on the "drop on first packet or gtfo" mentality, but still have to conquer the "well first you have to transfer the IP buffered packets into user space" mindset
ben_vulpes: but really it's ambiguous for a reason
ben_vulpes: the fbi's side - why would they argue apple's side?
ben_vulpes: the only line i have for coworkers and plebs on this topic is "you haven't thought for half a second why the /nsa/ didn't bring this suit?"
ben_vulpes: > juices flowing
ben_vulpes: gold, fluffypony
ben_vulpes: heh
ben_vulpes bites
ben_vulpes: i found one in rubby
ben_vulpes: why are all of the self-hosted rss readers written in php
ben_vulpes: tastes great with alf_dog
ben_vulpes: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-2.mediawiki and https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7.md, although the latter is only noted as a hardfork on a blog page
ben_vulpes: hue, ether's hardforking already?
ben_vulpes: what flavor of linux though?
ben_vulpes: looks like i changed nicks 7/29/2014
ben_vulpes: at mp's prompting i added a plastic handheld thing to the shower
ben_vulpes: sheesh this is like when i moved to new york and people were astonished to learn that there's electricity west of the rockies
ben_vulpes: i have tp ffs jurov
ben_vulpes: american pashtun!
ben_vulpes: AM PASHTUN
ben_vulpes shits in sink, eats from toilet bowl, never knew to do anything else before 2013
ben_vulpes: http://log.bitcoin-assets.com/?date=25-02-2016#1415503 << mount her on a bicycle, pilfer a bottle from the office, mash around the city on bikes, break onto the in-decomissionment sellwood bridge and fuck on it? iono man what does one do with random girls anyways
ben_vulpes: sure as hell beats drinking the horror at my own existence away
ben_vulpes: http://log.bitcoin-assets.com//?date=27-02-2016#1416923 << this girl i'm rather fond of convinced me that it wasn't a half-bad way to spend thirty years while my brain rots building apps for various usg tentacles.
ben_vulpes: mhm sure
ben_vulpes: > verify with text message (most secure)
ben_vulpes: phf: i humbly bring lolz: http://www.everetthousehealingcenter.com/
ben_vulpes: b6: what is an icebreaker?
ben_vulpes: homie
ben_vulpes: straight from the streets yo
ben_vulpes: mircea_popescu: gutter cascadian lingo
ben_vulpes: b6: ^^
ben_vulpes: how through a ddos did you get here?
ben_vulpes: neat phf
ben_vulpes: oh i see
ben_vulpes: http://log.bitcoin-assets.com/?date=28-02-2016#1417448 << btcfs, btcos, btclisp...
ben_vulpes: http://log.bitcoin-assets.com/?date=28-02-2016#1417563 << right, good point. what other commands aren't candidates for porting?
ben_vulpes: phf: ah! serialization.
ben_vulpes: srsly.
ben_vulpes: !up TheRealJohnGalt are we through the netsplit and can i yell at you about your flapping connection yet?
ben_vulpes really to bed now
ben_vulpes: sing songs from mary poppins while reading gpg-grams to defeat the high-fidelity microphones!
ben_vulpes: mirror terminal output and learn to read backwards!
ben_vulpes: rot13 in your ssh!
ben_vulpes: more random stacks are more secure!
ben_vulpes: punkman: aha would you like a stack randomizer while we're at it?
ben_vulpes: punkman: BUT IT'S ONLY USED IN SETGENERATE OMFGWTFBBQ
ben_vulpes: AaronvanW: cheers
ben_vulpes: AaronvanW: you want "sasl", and to instruct whatever client you're using to not join channels until it's done swizzling the sasl
ben_vulpes: phf, asciilifeform: this is a real treat to work with
ben_vulpes: anyways, i'm off to bed. thanks punkman.
ben_vulpes: !up AaronvanW
ben_vulpes: AaronvanW: your connection details are leaking before your host gets applied
ben_vulpes: why not just throw nGPL into WriteSetting?
ben_vulpes: assigns nLP equivalent to nGPL and throws it down the chute?
ben_vulpes: punkman: yeah i have nfi
ben_vulpes: punkman: yeah, a bool there doesn't make sense because it's used as a number of processors.
ben_vulpes: the others are all trivial
ben_vulpes: get-difficulty is a straight rip of the c from bitcoinrpc.cpp
ben_vulpes: well thanks to phf's fine work, i implemented get-connection-count, get-difficulty, get-generate, and am going to sleep on set-generate.
ben_vulpes: a casual browsing of the source suggests to me that the processor limiting could be excised. thoughts?
ben_vulpes: http://btc.yt/lxr/satoshi/source/src/bitcoinrpc.cpp#0266 << what does it mean for `nLimitProcessors = nGenProcLimit` to be passed as the argument to WriteSetting? an implicit test returning a boolean doesn't make much sense to me as a value for nLimitProcessors
ben_vulpes: half-baked exclamations of disgust are probably best kept here
ben_vulpes: like...what?
ben_vulpes: what i appear to have forgotten since the last time i looked into this pit of snakes is that it calls all of the rpc functions in turn to construct the help list.
ben_vulpes: right?!
ben_vulpes: and yes, yes. the whole rpc wart must be frozen with nitrogen and smashed into a zillion pieces.
ben_vulpes: http://btc.yt/lxr/satoshi/source/src/bitcoinrpc.cpp#0119 << well this will have to go
ben_vulpes: punkman: wasn't that forever ago? or is there a new case
ben_vulpes: now to wire in compile-and-load-file
ben_vulpes: finds car and set-car!
ben_vulpes: apropos does a thing
ben_vulpes: eee
ben_vulpes: phf: get to bed before i bog you down in emacs config arcana
ben_vulpes: this is a mega patch
ben_vulpes: ty phf
ben_vulpes: doooope
ben_vulpes: herp derp
ben_vulpes: a no
ben_vulpes: nope, eval error unbound
ben_vulpes: ^^ to haunt your dreams
ben_vulpes: error in process filter: net-read error: (cl-assertion-failed (cl-plusp length))
ben_vulpes: Connecting to Swank on port 1336..
ben_vulpes: nn phf great work
ben_vulpes: age trumps r/w load eh?
ben_vulpes: full of bad ideas tonight, me
ben_vulpes: mebbe call it "press party"
ben_vulpes: myeah, i figured.
ben_vulpes: also signers line i think is broken
ben_vulpes: phf: consider linking to sigs from patch page?
ben_vulpes: what a time to be alive
ben_vulpes: ^^ natively on the mac
ben_vulpes: 0
ben_vulpes: #> (btc-connections)
ben_vulpes: you people seem to think that i actually handle the rods myself
ben_vulpes: you'll probably want to re-grease the decompilator with some euros while we're at it, that never hurts and can frequently improve end-user experience
ben_vulpes: i recommend a thorough course of benjies, piped straight through the developer funnel.
ben_vulpes: myup, looks like y'all got a wad of javascript
ben_vulpes kicks tires, spits
ben_vulpes: ho ho ho
ben_vulpes ducks
ben_vulpes: clearly you need more to do
ben_vulpes shrugs
ben_vulpes: oh huh
ben_vulpes: hey phf this btcbase thing would rule with anchored line numbers on patches
ben_vulpes: aha i assumed, just thought it funny how quickly that number got bigger and by how much
ben_vulpes: heheheh strbuffsize goes from 256 to 2048
ben_vulpes: what a night
ben_vulpes: heavens to betsy
ben_vulpes: holy fuckadoodle phf delivars
ben_vulpes: init file, scuse me
ben_vulpes: Error: If Shiva is enabled, MUST specify init file!
ben_vulpes: lemme see if it shits to disk
ben_vulpes: at least, complains of no shiva flags
ben_vulpes: phf, asciilifeform: where is an appropriate place for custom trb scheme, and what mechanism should load it? just appending to the bottom of init.scm feels wrong.
ben_vulpes: this is idiomatic c and scheme?
ben_vulpes: phf: and in the c function declarations?
ben_vulpes: asciilifeform: is it inane of me to ask about hyphen/underscore conventions in shiva.cpp?
ben_vulpes: asciilifeform: okok! point taken.
ben_vulpes: i'm off to waft the child through hipstergenic clouds of pot smoke
ben_vulpes: anyways, rather neet. looking forward to shortening my loop up.
ben_vulpes: you're a real rubro now phf!
ben_vulpes: yeah i imagined that running buildroot wouldn't make sense on a bsdalike
ben_vulpes: v. cool
ben_vulpes: nifty, phf!
ben_vulpes: s/alive/aside
ben_vulpes: dash/hyphen conventions alive, ^^ asciilifeform, phf, mod6_, mircea_popescu
ben_vulpes: 0
ben_vulpes: #> (btc_connections)
ben_vulpes: ;)
ben_vulpes: how bout dem clang scripts
ben_vulpes: hey phf
ben_vulpes: hey
ben_vulpes: okay i'll leave that and the slime work to the real artisans
ben_vulpes: > allowing for reentry << bleeee
ben_vulpes: ;;later tell trinque BEHOLD http://www.businessinsider.com/meta-glasses-could-be-future-of-work-2016-2?r=DE&IR=T
ben_vulpes: phf: mebbe rewrite the syncing loop?
ben_vulpes afk for a bit, if not the eve
ben_vulpes: phf: i don't quite know yet. i'm just barely a code-technician, creativity and imagination's another 5-7 years off for me.
ben_vulpes: asciilifeform (phf, adlai, mod6_, mod6): okay this is grand and i can see several rpc commands trivially slain in this vein, and others with application of work. but but but! would someone send me a map for running /scheme/ code from within satoshis abortion?
ben_vulpes: i thought we considered that glass left on the floor for barefoot burglars
ben_vulpes: asciilifeform: what's the thinking behind using IMPLEMENT_RANDOMIZE_STACK in shiva.cpp?
ben_vulpes: quite the netsplit.
ben_vulpes: satoshi bless the noobs, for they bring lulz and drama.
ben_vulpes: ^^ nifty, asciilifeform! thanks for bearing with my thickness.
ben_vulpes: 399924
ben_vulpes: #>(btc-get-best-height)
ben_vulpes: have fun in meatspace, i'll derp through it.
ben_vulpes: i believe so, yes.
ben_vulpes: should have communicated to me that 201 did not supercede 198
ben_vulpes: the very same. <<
ben_vulpes: Apply the pedigree bridge path, re-name the directory to shiva, and you get
ben_vulpes: >
ben_vulpes: was i not to interpret "rebake using the correct v-tron" as "supercedes previous missive"?
ben_vulpes: before you bail
ben_vulpes: thank you for the very explicit directions, asciilifeform .
ben_vulpes: so to recap: tinyscheme_genesis, tinyscheme_snip, repl_fix, and then flag_bug_fix?
ben_vulpes: yeah, staring at it
ben_vulpes: http://log.bitcoin-assets.com//?date=21-02-2016#1411369 << i am failing to turn this thread into usable actions
ben_vulpes: so i should be able to leave the tinyscheme dir as tinyscheme? or am i screwing up royally in that my patch applications don't result in a shiva dir?