Show Idle (> d.) Chans
← | Results 22751 ... 23000 found in trilema for 'f:ben' | →
ben_vulpes: continue. The pain is terrible. With his tongue he mashes shit against the roof of his mouth and begins to chew, thickly now, the only sound in the room. . . .
ben_vulpes: putrefaction of corpses, it was the sovereign smell of their first meeting, and her emblem. The turd slides into his mouth, down to his gullet. He gags, but bravely clamps his teeth shut. Bread that would only have floated in porcelain waters somewhere, unseen, untasted—risen now and baked in the bitter intestinal Oven to bread we know, bread that’s light as domestic comfort, secret as death in bed . . . Spasms in his throat
ben_vulpes: with his lips, sucking on it tenderly, licking along its lower side . . . he is thinking, he’s sorry, he can’t help it, thinking of a Negro’s penis, yes he knows it abrogates part of the conditions set, but it will not be denied, the image of a brute African who will make him behave. . . . The stink of shit floods his nose, gathering him, surrounding. It is the smell of Passchendaele, of the Salient. Mixed with the mud, and the
ben_vulpes: But thoughtful Pointsman, anticipating this, has been sending laxative pills with her meals. Now her intestines whine softly, and she feels shit begin to slide down and out. He kneels with his arms up holding the rich cape. A dark turd appears out the crevice, out of the absolute darkness between her white buttocks. He spreads his knees, awkwardly, until he can feel the leather of her boots. He leans forward to surround the hot turd
ben_vulpes goes looking for shitposts
ben_vulpes: love the shit
ben_vulpes: swallow the shit
ben_vulpes: embrace the shit
ben_vulpes: ascii_field: embrace the webshit. iframe to signed thinger!
ben_vulpes: trinque: continuing our windowing and emacs sojurn: https://github.com/ch11ng/exwm
ben_vulpes: ascii_field, mircea_popescu: didn't hanbot teach us about the dangers of html and gpg earlier?
ben_vulpes: poor mod6 can't catch a break around here
ben_vulpes: !v assbot:ben_vulpes.rate.n6.1:e630ded4962e532d208a74d782ea9c37451b0858c31fb4280fd9f2c7ddce525e
ben_vulpes: !rate n6 1 crusty blood
ben_vulpes: !gettrust n6
ben_vulpes: n6: d'you plan to get into the wot as well?
ben_vulpes: n6: i understand that this is not a welcome message.
ben_vulpes: i recommend spinning up an aws gentoo instance. i've given up on macos support for this project.
ben_vulpes: you're on your own brave soul
ben_vulpes: ah well
ben_vulpes: n6: are you running on os x?
ben_vulpes: n6 i have no idea, buddy
ben_vulpes: there's always /patches.html...
ben_vulpes: mod6: not that my browser will do anything with the patch files but download them.
ben_vulpes: n6: all of my noodling on the topic resides at http://cascadianhacker.com/bitcoin/callgraph/
ben_vulpes: !up n6
ben_vulpes: we're just exploring the possibility space here
ben_vulpes: ascii_field: has warez?
ben_vulpes: punkman: hell if i know
ben_vulpes: meep. sorry.
ben_vulpes: addrProxy = 127.0.0.1:9050
ben_vulpes: fUseProxy = 0
ben_vulpes: fMinimizeOnClose = 0
ben_vulpes: fMinimizeToTray = 0
ben_vulpes: nTransactionFee = 0
ben_vulpes: fGenerateBitcoins = 0
ben_vulpes: nFileVersion = 50400
ben_vulpes: Loading wallet...
ben_vulpes: block index 63562ms
ben_vulpes: LoadBlockIndex(): hashBestChain=00000000000000000dfc height=367850
ben_vulpes: Loading block index...
ben_vulpes: addresses 26456ms
ben_vulpes: Loaded 39823 addresses
ben_vulpes: dbenv.open strLogDir=/home/ec2-user/.bitcoin/database strErrorFile=/home/ec2-user/.bitcoin/db.log
ben_vulpes: Loading addresses...
ben_vulpes: Default data directory /home/ec2-user/.bitcoin
ben_vulpes: Bitcoin version 0.5.4-beta
ben_vulpes: what was the rollover patch called?
ben_vulpes: let me restart the thing and grab the whole bootup log for inspection
ben_vulpes: i was hoping you'd contradict my own conclusions, but alas.
ben_vulpes: asciilifeform: my coracle's been wedged at 367850 since last night, even with the new db locks config. last 500 lines of debug.log: http://dpaste.com/1XB21DH.txt , please let me know if more would be useful
ben_vulpes is not terrifically familiar with the git gpg integration
ben_vulpes: interdasting
ben_vulpes: git produces patches tho--
ben_vulpes: <Adlai> ootb, signed patches. deeding signed patches from darcs is less work than doing so from git etc << how so? i've never touched darcs, the question comes from ignorance.
ben_vulpes to have a brow soothed on a sweet busom
ben_vulpes: i have no answers, only this hill to watch.
ben_vulpes: shall we demand that of the pete_dushenskis and hanbots who wish to run their own hand-compiled foundation releases?
ben_vulpes: <asciilifeform> ben_vulpes: yes, and that ought to be in every release << and this raises another question, shall mod6 and i now switch our build process to involve the rotor assemblage?
ben_vulpes: helps, somewhat.
ben_vulpes: mine explode at the line that fails instead of airily carrying on as though nothing happened.
ben_vulpes: asciilifeform: instructions rot, are dependent on fallible humans. i write scripts.
ben_vulpes: aha trinque's decisionmachine emerges!
ben_vulpes: http://log.bitcoin-assets.com/?date=01-08-2015#1220389 << how long? my maxint_locks build appears to be chewing on this one, but i cannot actually tell.
ben_vulpes: note that i haven't.
ben_vulpes: in the meantime, know that these few hours per day *i* do have might be put to better use than derping of dirs.
ben_vulpes: i'll save my "eedjit points" for when i actually cannot resolve things myself.
ben_vulpes: no, for another read through and another hack at "etc. as before" will resolve this.
ben_vulpes: CLEARLY
ben_vulpes: no! for it is a merely a derpy directory structure issue that any sophomore can figure out
ben_vulpes: trinque: was there, saw, comiserated
ben_vulpes: tripped, fell, yelling in fury
ben_vulpes: tendon-snipped by "use your noggin, eedjit" instructions
ben_vulpes: now is when i admit that i've yet to successfully compile bitcoin with rotor
ben_vulpes: asciilifeform: the antecedents thing for one
ben_vulpes: a forest, not any particular tree
ben_vulpes: 'tis not the patches but the whole workflow
ben_vulpes: don't care, can operate anything made by humans
ben_vulpes would learn fossil
ben_vulpes: dunno, have asked twice now
ben_vulpes: ;;later tell jurov pretty please
ben_vulpes: heck, it'd be a huge improvement if /patches.html rendered in chronological order
ben_vulpes: i am now imagining all sorts of dumb things like patches contributed in ml 'threads'
ben_vulpes: decimation: and he does, regularly
ben_vulpes: mircea_popescu will likely run me through the "oh you're complaining here have some more of what irks you" chipper
ben_vulpes: oh don't mind me, i'm just grumpy about a frictive process
ben_vulpes to food
ben_vulpes: of course.
ben_vulpes: i will be off to eat shortly.
ben_vulpes: i'm not critiquing your patchstacking, note.
ben_vulpes: can we share a git repository yet?
ben_vulpes: i know this.
ben_vulpes: patches and signatures in the repository itself. i'd not be averse.
ben_vulpes: he can correct me if i'm wrong.
ben_vulpes: all i ever heard was "git=invitation for tard collaborators"
ben_vulpes: of course!
ben_vulpes: how much hell would i catch for sharing this with others?
ben_vulpes: *i* have a repo. *it* has a *stable* and an *experimental* branch.
ben_vulpes: i'm just trying to operate within these crazy boundaries. i don't have any process improvements that i'm sure wouldn't get shot down in a new york second from asciilifeform.
ben_vulpes: "what, you want to automate the nuclear power plant?"
ben_vulpes: "what, you want to automate this process that keeps the tards at bay?"
ben_vulpes: "what's so hard about applying patches to your private repository?"
ben_vulpes: "a real contributor would write all of their own tooling to solve this"
ben_vulpes: i can just imagine the arguments
ben_vulpes: !s testing in production
ben_vulpes: but this is bitcoin, where since time immemorial people have been shipping code that can only ever be tested in production and then standing by in amazement claiming that "nobody could have predicted!"
ben_vulpes: from experience i know that the more difficult it is to test the software, the less likely anyone is to actually do so.
ben_vulpes: this makes for quite the testing nightmare. those interested in testing must reverse applied patches to your antecedent tip and then apply yours.
ben_vulpes: if you're up to date on the patching, submit a patch and note its antecedents.
ben_vulpes: last release, i'd prefer. asciilifeform tends to stack his patches atop one another.
ben_vulpes: the fewer enforced constraints upon us, the more discipline with which we must act.
ben_vulpes: dvcs means we can all have a repo
ben_vulpes: decimation: i'm still 1.5klol behind
ben_vulpes: nevertheless.
ben_vulpes: grand exaggeration.
ben_vulpes: "i don't know, let's test it during code review"
ben_vulpes: "does it work?"
ben_vulpes: "here have a pull request"
ben_vulpes is struck by the eerie resemblance to $dayjaeorb here
ben_vulpes: mircea_popescu: broken << sure, yeah.
ben_vulpes: i'm all for barriers to entry here but this is a goddamn development obstacle course
ben_vulpes: fucked it up somehow
ben_vulpes: i tried once
ben_vulpes: "all testing" which is what we've seen to date.
ben_vulpes: say it again.
ben_vulpes: not that i'm not infinitely indebted to you for unwedging my coracle but a hint of context'd be useful.
ben_vulpes: here's your indication!
ben_vulpes: not even a note in correction about "lol sry first patch doesn't work"
ben_vulpes: so ofc i /try/ first patch
ben_vulpes: second patch contained a link to mp's "dis wat i do, yo"
ben_vulpes: started at ml, canonical information repository.
ben_vulpes: plz for to slightly more detail in patchdescs.
ben_vulpes: "let me see"
ben_vulpes: "does it work?"
ben_vulpes: "here's a fix"
ben_vulpes: so i am to expect that patches arriving in the ML aren't even tested now?
ben_vulpes: that's the one i'm using!
ben_vulpes: asciilifeform: did you find a reason why maxint wouldn't work, or is the second patch just using mircea_popescu's lock values for 'myzteeri0us reezuns'?
ben_vulpes: the first, asciilifeform
ben_vulpes: maxint_locks
ben_vulpes: however the build i made on 7-15 with the dumpblock patch boots from the same datadir.
ben_vulpes: myes, i agree.
ben_vulpes: db.log, sir.
ben_vulpes: i'll try to nuke some state and come back with more useful information.
ben_vulpes: asciilifeform: i don't even see it doing anything with strace
ben_vulpes: has anyone else compiled the maxint patch and received db.log errors of "unable to join environment"?
ben_vulpes: !s unable to join
ben_vulpes: <mircea_popescu> increasingly, becoming a problem i nthe us, too. << tell me about it
ben_vulpes: an surfeit of things to do and people to do them
ben_vulpes is alive, barely
ben_vulpes: what brings you /back/, jordandotdev?
ben_vulpes: "just clobber the lusers computer"
ben_vulpes: s/problem/fun/
ben_vulpes: this is the industry standard approach to the by-now-all-too-familiar-#b-a-bitcoin-dependency-problem
ben_vulpes: evening, hanbot
ben_vulpes: "we can, therefore we must"
ben_vulpes: just a joke
ben_vulpes: (but ascii - i /can/ mutate in place, therefore i /must/!)
ben_vulpes: am reading, yes
ben_vulpes: this has come up before, and i had forgotten.
ben_vulpes: well how'd i know without putting myself up for the cane
ben_vulpes: ;;later tell phf http://paste.lisp.org/display/152828#1 << do forgive my ignorance, but what am i missing about converting the "command" into a string? (Adlai, asciilifeform, your eyes'd be appreciated too)
ben_vulpes: i don't see any usage of anysubscribed at least, asciilifeform
ben_vulpes: readable, renderable...
ben_vulpes: but i never did.
ben_vulpes: asciilifeform: mircea_popescu did iirc, via gimp
ben_vulpes: gaze ye and weep
ben_vulpes: ehuhueeuhe
ben_vulpes: <TheNewDeal> a new deal of sorts << i will give you points for this even if nobody else will
ben_vulpes: <mircea_popescu> grats, i guess ? o.O << hyuuuuahahaha
ben_vulpes: <BingoBoingo> http://log.bitcoin-assets.com/?date=01-08-2015#1221623 << I made a point of hunting 1990's keys from universities to feed the Phuctor. Many were of short length. I though maybe they'd fall first and prime the beast, but... << bb you're awesome
ben_vulpes off for a bit
ben_vulpes: whence the extra data? most of the relationships should live in foreign keys.
ben_vulpes: but transaction indexing etc should take *that* much space...
ben_vulpes: kakobrekla: 'toshi' creates its db from a rails schema iirc, no surprise that it's 10x blockchain size
ben_vulpes: ah jesus insight is a shitshow that much i know from pissing on the fence in question
ben_vulpes kicked off its indexer this morning
ben_vulpes: aside from "can't serve while indexing lol"?
ben_vulpes: why is abe so bad?
ben_vulpes: o well then
ben_vulpes: which to avoid, which are not miserable?
ben_vulpes: kakobrekla: ever run an 'abe'?
ben_vulpes: 'twas a joke, joke only.
ben_vulpes: so stop doing it or stfu
ben_vulpes: welcome, trinque
ben_vulpes: ;;later tell phf %%
ben_vulpes: phf: your .dat reader works very well, thank you. consider submitting to list?
ben_vulpes: TODAY I DO BATTLE WITH PYTHONPATH
ben_vulpes: probably an uninteresting question.
ben_vulpes: what i do not understand is why it is necessary to iterate through mapblockindex.
ben_vulpes: myes, i follow.
ben_vulpes: this is above my pay grade in terms of data structures, but perhaps an opportunity to learn. is there not a data structure available for use that doesn't have to iterate through the whole index to grab the element of interest?
ben_vulpes: + // possibly could be improved if we descend from best height if requested height is closer to it
ben_vulpes: + // this is O(n^2)...
ben_vulpes: no no no
ben_vulpes may be wrong, is undercaffinated, girl is stil making breakfast.
ben_vulpes: asciilifeform: location of block on disk, though?
ben_vulpes: it's like a surfboard for the sky!
ben_vulpes: shocking how quickly my equilibrium returned
ben_vulpes: $bizpartner took me up in a 2 seat glider the other weekend, after about .75 hrs of going in a circle to the right i asked to come down, was put on the stick and pedals instead.
ben_vulpes: davout: sounds like a lot of work. congrats etc.
ben_vulpes: (see asciilifeform's comment re upper bound of dumpblock)
ben_vulpes: trinque: it's a crime that there are no transaction indices or block indices.
ben_vulpes: similar to how all blublangs implement conditions poorly.
ben_vulpes: myeah. curse of the kv user.
ben_vulpes: how's life, davout? haven't seen you much of late.
ben_vulpes: besides, you'll need to write a bitcoind of your own some day anyways.
ben_vulpes: don't worry about wasted effort. the more people who have it in their head, the better off la serenissima is.
ben_vulpes: trinque: "many eyes"
ben_vulpes: hi davout
ben_vulpes: not getting ddosed? not useful.
ben_vulpes: the fate of all useful things connected to the internet without mitigation
ben_vulpes: isn't processmessages the only thread that writes to the db?
ben_vulpes: myes, have read.
ben_vulpes: then i read the logs.
ben_vulpes: i imagined that he of many hands had actually excised the locks.
ben_vulpes: imagine my extreme disappointment when i cracked my email this morning, found a "bullet" for the locks, and opened it to find a config change.
ben_vulpes: s/in/from
ben_vulpes: phf: we're drinking and talking about how to persist data appropriately in cl proggies as we speak
ben_vulpes: p nice, phf
ben_vulpes: hey phf how much of bitcoind have you implemented in common lisp yet?
ben_vulpes: eeeeeeeeeeeeeeeeeeeeeeeee
ben_vulpes: !s -e
ben_vulpes: gernika: see above
ben_vulpes: !s gentoo guide
ben_vulpes: and i'm not quite sure what the "select * from Y" equivalent in a cl proggie would be
ben_vulpes: "statice"
ben_vulpes: myeah, sure
ben_vulpes: perhaps old system serializes its memory to disk before shutdown?
ben_vulpes: i understand s-l-a-d, but not necesarily how to persist in-memory data structures over the running of a new system.
ben_vulpes: i'm not quite certain how persistence is supposed to work in the absence of an external database, and over restarts/redeploys.
ben_vulpes: poor man's consistency check?
ben_vulpes: (defmethod (setf side-a) :after ... ) runs after someone calls (setf (side-a instance-of-triangle-class))
← | →
Random(trilema) | Download hourly DB snapshot | Get Source Code