a111: Logged on 2017-12-27 03:43 mircea_popescu: let me put it this way, maybe resolves problem : v unpermits a specific kind of hack within the purview of this discussion, wherein one tries to design after the fact. correctly designed items will have the larger bits (by footprint) earlier in the patch tree ; and fray out correctly. github-style nonsensica commonly attempts to discover that "hey, this johnny come lately item should have been an evie-comes-early MODULE, let'
mircea_popescu: what i mean by http://btcbase.org/log/2017-12-27#1758994 is specifically that i suspect the ONLY reason one might wish to merge is that one failed to design the item he's hacking.
mircea_popescu: the burden where it belongs -- why permit merges ?
mircea_popescu: whereas K would be wrong to attempt same, and instead should regrind a whole new genesis, call it D, even if it is made up of the reunion of the As and Bs he uses.
mircea_popescu: now, the v doctrine as it stands right now, both on logs and actual precedent, at least as far as i understand it (but this is vacuous both as a representation and as a history, as most important questions haven't yet been seriously tested) -- is that Z is right to simply sign a patch on B-genesis ;
mircea_popescu: toghether so far ?
mircea_popescu: at this moment, if lord K observes that he could use the tree of X up to A2 and the tree of Y up to A3 ~together~ he could install D4 on this pile and similarily to Z produce a different still useful item.
mircea_popescu: then along comes lord Z, and this lord Z observes that if he used B3 and instead of B4 installed C4 on the same top, he'd get a wholly different but entirely useful to him item. so he makes this.
trinque: because the hashes are hashes of touched files
mircea_popescu: in preference of regrinding the item ?
a111: Logged on 2017-12-05 13:27 mircea_popescu: no but see, we use different terminology. i do not assign anything to "code written". the source of code, to my eyes, is he in the wot who has read it.
mircea_popescu: if you signed it, then you read it. what matters what you edited ? moar of the same http://btcbase.org/log/2017-12-05#1746388
trinque: sure, in the vpatch would be "I require this list of antecedent items, subset S of which I intend to change thus"
trinque: back briefly on the frayed rope, what's harmful about naming an antecedent that you didn't edit, but require
mircea_popescu: a lesson for all future minds in there.
mircea_popescu: there's no difference i can observe between indiancandy scratching at the door and satoshi scratching at the door. there's a way to get in -- getting in "on their own terms" is not on the table at all.
mircea_popescu: man did not bother, which can only be rendered as "man told us in no uncertain terms to fuck off", well... the sentiment is mutual.
mircea_popescu: relevancy is dearly bought ; man wanted to still be in the genesis of 2017, man should have made proper db calls, proper logs, etc.
trinque: proper hypertext system (itself based upon v) provides the talmud commentary thing endlessly
mircea_popescu: whosoever deeply cares about the historically irrelevant accident of windows-bitcoin-0.1 is more than welcome to diff his own sources of that against tmsr-bitcoin
trinque: asciilifeform: as a carving tool for the graph of knowledge
mircea_popescu: under the authority of the republic ; not trying to enact selves out of the well threadbare wizard cloak of satoshi.
asciilifeform: then why v at all
mircea_popescu: so for instance, "genesis a proper db ; then patch in three different branches for the three different types of node envisaged" doesn't seem on the face problematic.
trinque: anyhow lemme run at it again. you can't modularize because you have to fake work in a disparate part of the tree to merge
mircea_popescu: ie, i don't expect the trb cut as described to have a trb genesis necessariyl, or even probably.
mircea_popescu: there's nothing wrong either in principle or in practice with making a correct item as the genesis and then patching in various parts of trb.
trinque: these aren't "trb" except in shitworld
trinque: in that these are distinct items.
mircea_popescu: well, i am kind of a fan of the whole "v doesn't permit you to lie to yourself about having supposedly designed what's utterly an ad-hoc item".
trinque: this is what I meant actually, by "can't modularize" within same walk of the v tree
mircea_popescu: now, is this enforcement a problem with v, is the proposition ? or is the aforegoing a misrepresentation of the discussion ?
mircea_popescu: let me put it this way, maybe resolves problem : v unpermits a specific kind of hack within the purview of this discussion, wherein one tries to design after the fact. correctly designed items will have the larger bits (by footprint) earlier in the patch tree ; and fray out correctly. github-style nonsensica commonly attempts to discover that "hey, this johnny come lately item should have been an evie-comes-early MODULE, let'
trinque: I'm actually writing right now on how the hypertext thing relates
trinque: cannot without the 'add comment to files you needed' ritual
trinque: means for example that db-interaction routines are in one file, network interactions in another.
a111: Logged on 2017-12-27 01:41 trinque: http://btcbase.org/log/2017-12-27#1758909 << if vtronic software is the same frayed rope, no one can ever modularize within the same v-tree. this may be a feature.
mircea_popescu: "hey, aren't you worried your shitcoin will get altcoin'd in the near future ?" "no, i am dog and i don't understand anything. vote me!"
mircea_popescu: lmao fucktard. a) the "pirate party" scam utterly fucking failed, how about addressing THAT ; b) kinda hard to have anyone ditch an empty ship, huh.
a111: Logged on 2017-12-19 18:04 asciilifeform: we actually had the ast-diff thread, re phf's lisp diff lament.
asciilifeform: but this is reaching into the fantastic.
asciilifeform: or, on other end of the possible, a vtron that somehow understands that a call of foo necessarily depends on the patch that birthed foo... and requires disambiguation only if >1 foo exists in the tree
asciilifeform: i'd like to encourage trinque to put some of his 'crackpot' algos 'to paper', as articles. the hypertext thing was interesting imho, for instance, and so was earlier trinque pill for 'mining is a bug', and possibly other occasions. dun be afraid to write down conjectures, trinque , gauss did
asciilifeform: trinque: if you have concrete algo to align these -- i'm all ears
trinque: asciilifeform: is possible, but deserves to be in the logs
trinque: to my mind the hash is currently putting too narrow a constraint on the context within which the current patch is to be applied, where we could broaden the context at no detrimental, and possibly beneficial cost
a111: Logged on 2017-12-26 21:22 trinque: http://btcbase.org/log/2017-12-26#1758679 << to my mind this suggests the hashes present in vpatch blocks are wrong. if they were rather the hash of the entire concatenation of the diffed item before and after applying that block, there'd be no need to pointlessly edit files to continue on the same branch.
asciilifeform: ( btw is there an engl. equiv of that term ? i'd like to learn it )
asciilifeform: that was a case when 'put in a comment to align vtronics and semantics' would have been The Right Thing
asciilifeform: asciilifeform introduced the schemetron 1st, and only 2nd the glue in trb, and they were not automagically v-linked
a111: Logged on 2017-12-21 17:38 mircea_popescu: anyway, continuing the trinque discussion, it seems entirely unavoidable that trb will become 3 things : a wallet node, optimized for pumping out local signed tx ; a block node, optimized for keeping the blockchain, getting blocks, no mempool nonsense ; and a spy node, optimized to keeping track of the lies and nonsense flowing through the relay network (mempool, timing nodes, what have you).
trinque: so then, when things get so modular that you have frayed rope, author makes clean separation, as V has told him he has distinct items.
asciilifeform: trinque: i actually put a good bit of thought into the vtronic shape of ffa, while rewriting it ( current-day ffa , observe, is a rewrite, largely by hand, of the previous )
trinque: in either case, what does asciilifeform think of the ritual of "add comment to unrelated file to merge paths", not symptomatic of a problem?
trinque: it again runs into the unix idiocy of "file", though, because file does sometimes mean module, sometimes means subcomponent of module.
a111: Logged on 2017-12-27 00:46 mircea_popescu: http://btcbase.org/log/2017-12-27#1758883 << sure. in the sense blockchain is frayed rope, this also.
trinque: http://btcbase.org/log/2017-12-27#1758909 << if vtronic software is the same frayed rope, no one can ever modularize within the same v-tree. this may be a feature.
a111: Logged on 2017-12-27 00:49 mircea_popescu: http://btcbase.org/log/2017-12-27#1758901 << what's the problem with a "wasted" FZ anyway
asciilifeform: http://btcbase.org/log/2017-12-27#1758913 << it's not the wasted 8kbit or whatnot ( though on e.g. fpga, that's real waste that you can take to the bank...) but the ~ugliness~
BingoBoingo: Eh, give it 10 years and everything Republican will be inconel while the last USG trinkets come in Chinese potmetal
a111: Logged on 2017-12-27 00:45 mircea_popescu: http://btcbase.org/log/2017-12-27#1758864 << you engage in a category error. you don't know what's in the box BEFORE opening the box.
asciilifeform: http://btcbase.org/log/2017-12-27#1758907 << the reason engineering is even possible , is that it is not necessary to open ~every~ box. sometimes can form quite accurate picture without spending whole life opening boxes, eating every rotten egg top to bottom etc
mircea_popescu: 20bux in the chinoshop
mircea_popescu: damned thing was the size of a god damned depth charge
BingoBoingo: Will probably start upping the blog frequency to let some more vemon out
BingoBoingo: Anyways thinking on the noob roughing up earlier, could be a side effect of tranquility overdose. Gotta torture betas.
BingoBoingo: Hence the spankings and vacuum cleaner tube
mircea_popescu: a sense of confort, the common woman's mindeater.
BingoBoingo: <mircea_popescu> http://btcbase.org/log/2017-12-26#1758819 << she kinda got sent off for NOT being looking dedicatedly enough ; then she got pissy because i imagine in her dumb head she had self-delusions as to self-importance as dear as they were baseless. << Ah, gets BTC once returns years later and has less sense and more ideas
mircea_popescu: anyway, maybe the correct approach re the l0de thing would be something like a simulcast interview. you do interviews l0de ?
mircea_popescu: http://btcbase.org/log/2017-12-27#1758901 << what's the problem with a "wasted" FZ anyway
a111: Logged on 2017-12-27 00:23 asciilifeform: http://btcbase.org/log/2017-12-26#1758779 << i see e.g. trb tree, as the frayed end of a rope. in long term, observe, the loose ends that dun get built on -- fade away, like orphan chains. btc is actually more or less same kind of system. but iirc we had this thread.
mircea_popescu: http://btcbase.org/log/2017-12-27#1758883 << sure. in the sense blockchain is frayed rope, this also.
a111: Logged on 2017-12-27 00:06 asciilifeform: let's say every homo redditus alive -- suddenly interested. then WHAT? what's gained, other than a great mass of meat that now gotta be put somewhere far from the reactor rods
mircea_popescu: http://btcbase.org/log/2017-12-27#1758864 << you engage in a category error. you don't know what's in the box BEFORE opening the box.
a111: Logged on 2017-12-26 18:15 ben_vulpes: and in other profitable mining strategies: https://www.nytimes.com/2017/12/25/business/energy-environment/germany-electricity-negative-prices.html
asciilifeform: http://btcbase.org/log/2017-12-26#1758681 << if there existed anything like a market in (reasonably recent) miners -- they'd already be installed at the plant, in place of those gigantic resistors . ( and iirc there was a mircea_popescu thread, involving e.g. fish ponds )
asciilifeform: which is roughly 4x the typical ( thing's been floundering since late august ) rate.
asciilifeform: in other noose, zoolag with 'aggression' : walked from 484621 to 495973 in ~60 hrs.
asciilifeform: http://btcbase.org/log/2017-12-26#1758743 << this historically worked CONSIDERABLY better than 'let's throw the reddit toilet into reverse gear and see what crawls out of the pipe'
asciilifeform: what is with this eagerness to pointlessly blunt the knife. i dunget it !
a111: Logged on 2017-12-26 21:22 trinque: http://btcbase.org/log/2017-12-26#1758679 << to my mind this suggests the hashes present in vpatch blocks are wrong. if they were rather the hash of the entire concatenation of the diffed item before and after applying that block, there'd be no need to pointlessly edit files to continue on the same branch.
asciilifeform: ( i.e. it is already inescapably linear. asciilifeform half-expected that the kakoschism would produce a long-playing split of the trb universe, but neverhappened. not every possible thing, happens... )
asciilifeform: http://btcbase.org/log/2017-12-26#1758779 << i see e.g. trb tree, as the frayed end of a rope. in long term, observe, the loose ends that dun get built on -- fade away, like orphan chains. btc is actually more or less same kind of system. but iirc we had this thread.
asciilifeform: and how big will be the vtron ? mine was <400 lines. imho this is worth something. and every feature added, comes at a cost.
asciilifeform: every time think of a possible change : think, does this take it in the direction of heathendom ? can it still make a patch like http://btcbase.org/patches/asciilifeform_aggressive_pushgetblocks , where it is hammer-in-your-face-obvious to the reader that every single fucking line does ?
asciilifeform: i would like everybody who is itching to change the way v fundamentally works, to sit down and think about why we ain't using 'git' etc.
asciilifeform: i should not need to look for a meta-document (with own sig, presumably) to know which group of patchons constitutes e.g. 'asciilifeform_dns_thermonyukyoolar_kleansing' .
a111: Logged on 2017-12-26 21:42 phf: we also at some point had a thread, where i believe ascii but also others were leaning towards the idea of a single file vpatches (i.e. that a vpatch should only ever contain hunks for a single file). i'm starting to think that multi-file solutions in general are a hack ("we can't fit the entire compilation in memory"), but then i've been looking at TeX on one hand, and the "millions of support files" in diff/patch on the other
asciilifeform: http://btcbase.org/log/2017-12-26#1758790 << this'd eat away substantially at the human-readability of the vpatch. which imho is a key property.
a111: Logged on 2017-12-26 21:36 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"
asciilifeform: http://btcbase.org/log/2017-12-26#1758781 << this only oughta be done in 2 situations -- 'releases' , as discussed by mod6 et al ; and to avoid fuckuppy as seen in orig shiva patch, where there was a logical dependence , but not a vtronic one , b/w shiva-part1 and -part2
asciilifeform: which, in the whole picture, does not come close to topping the list of the hardest labours of a trb experimenter
asciilifeform: but you can replicate same effect by pressing by the press rules, and then copying by hand.
asciilifeform: ( it was , naturally, by having , at least in the early history, the tree from which each of the 'sibling' patches was produced, on account of having produced'em ) .
a111: Logged on 2017-12-26 21:42 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
asciilifeform: http://btcbase.org/log/2017-12-26#1758788 >> 'The founder also promised that in addition to the common practice of crediting BTC holders with equivalent balances of the new coin (B2X), they would also receive “a proportional number of Satoshi Nakamoto’s Bitcoins as a reward for their commitment to progress.”' << lol!!
asciilifeform: let's say every homo redditus alive -- suddenly interested. then WHAT? what's gained, other than a great mass of meat that now gotta be put somewhere far from the reactor rods
a111: Logged on 2017-12-26 22:06 l0de: to get viewers of my show interested in their political goals
a111: Logged on 2017-12-26 23:02 mircea_popescu: http://btcbase.org/log/2017-12-26#1758790 << especially in the light of 1. move/rename 2. edit double-patch method this seems more and more like the right thing ; but then again what to do of regrinds ? regrind should ideally be "one patch out of many"
asciilifeform: http://btcbase.org/log/2017-12-26#1758834 << it is not clear to me why the current scheme ( leaving aside the idiocies of unix diff/patch, in particular the file moves thing ) is not satisfactory. i dun subscribe to the 'force beauty through mechanism' school of thought. it is the job of the patch author to make it behave acceptably in the target vtree, ~before~ releasing. and failures are of the author, not of the mechanicals.
asciilifeform: i suspect that not 1 could follow, e.g., the apeloyee noise floor thread.
asciilifeform: the problem with voice pirates, any and all who have ever at any point lived, is that they are reddit.
asciilifeform: the usg polizei prioritize the voice pirates, because they compete directly with the usg 'music' monopoly
a111: Logged on 2017-12-26 23:04 mircea_popescu: my original thought was "can we do something like the tits drip but for sw enthusiasts instead ?" ; alf pointed out thatr well, carrierless issue.
asciilifeform: http://btcbase.org/log/2017-12-26#1758839 << asciilifeform did a bit of survey of the sw spectrum ( where he lives , but also elsewhere, via helpful public toilet ip-streamed receivers. ) plenty of digital ???? in'ere. incl. in places where none 'ought', Officially, to be. but 1) could just as easily be usg 2) it's all, definitionally, carriered signal, or asciilifeform would never have learned of it
asciilifeform: http://btcbase.org/log/2017-12-26#1758841 << the real mega-puzzler is , what if anything are they capable of that is of any use whatsoever.
mircea_popescu: http://btcbase.org/log/2017-12-26#1758819 << she kinda got sent off for NOT being looking dedicatedly enough ; then she got pissy because i imagine in her dumb head she had self-delusions as to self-importance as dear as they were baseless.
mircea_popescu: if anyone's got an idea of how to construct the item though i'd much like to hear.
mircea_popescu: my original thought was "can we do something like the tits drip but for sw enthusiasts instead ?" ; alf pointed out thatr well, carrierless issue.
a111: Logged on 2017-12-25 19:34 mircea_popescu: and speaking of http://btcbase.org/log/2017-12-25#1758548 anyone got any ideas of how to meaningfully support the SW hobbist ?
a111: Logged on 2017-12-26 21:42 phf: we also at some point had a thread, where i believe ascii but also others were leaning towards the idea of a single file vpatches (i.e. that a vpatch should only ever contain hunks for a single file). i'm starting to think that multi-file solutions in general are a hack ("we can't fit the entire compilation in memory"), but then i've been looking at TeX on one hand, and the "millions of support files" in diff/patch on the other
mircea_popescu: http://btcbase.org/log/2017-12-26#1758790 << especially in the light of 1. move/rename 2. edit double-patch method this seems more and more like the right thing ; but then again what to do of regrinds ? regrind should ideally be "one patch out of many"
a111: Logged on 2017-12-26 21:40 phf: ben_vulpes: official trb releases touch many files to tie them all into a single endpoint, e.g. `makefile' did that
phf: If you have only the present report, not a tape, you will have to prepare files WEAVE.WEB and TANGLE.WEB by hand, typing them into the computer by following Appendices D and E. Then you have to simulate the behavior of TANGLE by converting TANGLE.WEB manually into TANGLE.PAS ; with a good text editor this takes about six hours.
trinque: shinohai, you are the baron titsbare himself; got any camhos that can read?
l0de: someone with a thick romanian\cambodian accent reading a statement they obviously do not understand
l0de: as they are internet neer-do-wells
l0de: to get viewers of my show interested in their political goals
l0de: I suggest the most serene republic air some sort of introductory statement
l0de: the funds have been remitted to my account
phf: i don't remember if there was any kind of interesting insight from the resulting graph, i should revisit it..
phf: in which case your graph connections become mandatory transitions (rather than what it is now, where you can technically press two different vpatches against a non-overlapping sets of files)
phf: i've also played around with treating vpatch as a container. there's a function on btcbase for splitting all of the vpatches into separate objects, that each hold a single file changes (it's called something like explode-vpatch)
ben_vulpes: also, single-file vpatches drives the system towards whole sourcetree hashing, otherwise they'll definitionally never depend on one another
phf: we also at some point had a thread, where i believe ascii but also others were leaning towards the idea of a single file vpatches (i.e. that a vpatch should only ever contain hunks for a single file). i'm starting to think that multi-file solutions in general are a hack ("we can't fit the entire compilation in memory"), but then i've been looking at TeX on one hand, and the "millions of support files" in diff/patch on the other
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
shinohai: Just in time for the holidaaaaaaaaaaays fake bitcoin returns
phf: ben_vulpes: official trb releases touch many files to tie them all into a single endpoint, e.g. `makefile' did that
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"
mircea_popescu: then if it is, trinque's point goes away because well... file hash as good as project hash for the linear bat.
diana_coman: onth "meaningful" there doesn't refer to code only and if new code in new files depends on existing code in untouched existing files, it may be meaningful nevertheless to update the readme file of the project for instance to say as much
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
mircea_popescu: trinque this is actually not altogether a meritless point.
diana_coman: I ran a bit into that with eucrypt but I can't say I have some clear idea what would be a good solution there as it seems to me it's a matter of level considered i.e. file, folder, component, whole project, what
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
a111: Logged on 2017-12-26 17:52 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?
trinque: http://btcbase.org/log/2017-12-26#1758679 << to my mind this suggests the hashes present in vpatch blocks are wrong. if they were rather the hash of the entire concatenation of the diffed item before and after applying that block, there'd be no need to pointlessly edit files to continue on the same branch.
borstal: Right Banks, you bastard! I'm the daddy now, next time, I'll fucking kill ya!
a111: Logged on 2017-12-26 19:46 BingoBoingo: At the rate things are moving by mid 2018, the demand for openess to get a lend of voice is likely going to be self performed rectal ultrasound on mfc while reading logs
BingoBoingo: There's chicas everywhere so if that fell through no big deal... The concerted effort put for by the locals on the Latino Christmas show, I lack the patience and means to make that happen on a whim.
BingoBoingo: One doesn not see the city in the splendid glow of burning metal salts in the sky without missing them.
BingoBoingo: Ah the lols to come from venue shopping n00bs
BingoBoingo: At the rate things are moving by mid 2018, the demand for openess to get a lend of voice is likely going to be self performed rectal ultrasound on mfc while reading logs
mircea_popescu: "avoidant" as per teh "attachment theory" nonsense that pantsuit "public policy" rests upon
diana_coman: the dangerous reflections, who knew
shinohai: mp-wp worked equally well on apache and nginx for me. Never used another db besides mysql tho
BingoBoingo: danielpbarron: How's the frozen north?
mircea_popescu: hanbot no but see, THIS is what a classical education fucking is. not retarded fry making hobbit jokes because hey, the history according to fry started when he first got a bit of usg.corp fried chicken.
hanbot: in other puns, i discovered just this morning that "hippopotamus" is the latin horse + river, had missed out on the double pun fun of http://trilema.com/2017/the-hippopotamus/ 's last line. i stand in awe and horror of whomever ends up adnotating trilema
mircea_popescu: so as the reconciler, you get to pick which of ~either~ a ~or~ b to count in your considered oppinion as the republican and which as the heretic.
mircea_popescu: the situation where a and b are pressed SEPARATELY is a fork.
a111: Logged on 2017-12-26 17:52 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?
mircea_popescu: http://btcbase.org/log/2017-12-26#1758679 << the ~only way to fix a tree that has diverged is to regrind that portion of the divergence you intend to keep.
mircea_popescu: "the arrangement leaves me stranded when eg trying to understand why hillary lost, but that's ok, i'm not really meant to understand things."
mircea_popescu: "oh, i read cnn for the commentary, the boobs are INCIDENTAL. also, fleshhouse and playcunt, same deal. oh and those letters to the editor ? totes legit!"
mircea_popescu: if one's stuck pretending something stupid, better off make it include being stupid rather than pretend it's possible to include some kind of being smart that doesn't readily reduce to being smrt.
mircea_popescu: better than the "professional" conceit. really, someone got to anchor tv for their non-cleavage skills ? what am i to believe next, that bridges are for sale ?
a111: Logged on 2017-12-26 15:19 shinohai: Does local TV have sexy weather girl BingoBoingo ?
mircea_popescu: http://btcbase.org/log/2017-12-26#1758666 << speaking of, /me saw fox something-or-the-other over at whorehouse/steakhouse yest. they had a chick with an ass/waist/boob range that was iiincredible, and then had her act like a retarded 12yo playing pattycake and whatnot with the blondy they had paired her up with.
ben_vulpes: and in other profitable mining strategies: https://www.nytimes.com/2017/12/25/business/energy-environment/germany-electricity-negative-prices.html
a111: Logged on 2017-12-26 01:06 mircea_popescu: http://btcbase.org/log/2017-12-25#1758589 << i don't get what the problem is. write a patch that modifies the filebase into the shape you want it to be. what's the problem ?
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?
BingoBoingo: And pantsuit climatarasty neglects that... when heat fuels 100% humidity... Rain tends to happen dropping the humidity again https://archive.is/k7j1f
BingoBoingo: And from the Spades and Spades departmento https://i.redditmedia.com/AQIpkdNnuUHHIyzGjCoT27cNXadOJaQXbMtC5IvJECg.jpg?w=603&s=680f4783200e1fcaac02a3c15602d477
deedbot: http://www.thedrinkingrecord.com/2017/12/26/other-assorted-trivia-on-navidad-in-uruguay/ << Bingo Blog - Other Assorted Trivia On Navidad In Uruguay
shinohai: Does local TV have sexy weather girl BingoBoingo ?
BingoBoingo: And this is how they do the weather here http://www.elpais.com.uy/informacion/mal-asi-estara-diciembre-enero.html
BingoBoingo: The current president issued a compasionate pardon allowing former president to die in a hospital rather than prison. The pantsuit fake news is alleging riots. Possibility of USG.blue color shennanigans.
shinohai: De nada .... what's happening in Peru, The Cuy is rising up?
BingoBoingo: In other news, god bless Peru for not having real datacenters. Sounds like a very inconvenient place to be right now.
shinohai: The whole series thus far is very entertaining.
asciilifeform: in other lulz, https://archive.is/Q0fc5 >> 'Thousands of government papers detailing some of the most controversial episodes in 20th-century British history have vanished after civil servants removed them from the country’s National Archives and then reported them as lost.'
deedbot: http://www.thedrinkingrecord.com/2017/12/26/as-it-turns-out-fireworks-do-not-photograph-well-navidad-in-the-land-of-tranquility/ << Bingo Blog - As It Turns Out Fireworks Do Not Photograph Well: Navidad In The Land Of Tranquility
BingoBoingo: zen_: Also do you have a blog, or any links to work which might impress the republic?
BingoBoingo: Or issue a plea for the chance to make your case again
BingoBoingo: And I got to skip the awkward waiting between mandatory check out and check back in times at the hostel
mircea_popescu: aand in other socialism-improved-college lulz, https://www.theguardian.com/us-news/2017/aug/21/chicago-was-sexual-fantasy-of-us-professor-and-oxford-college-worker
mircea_popescu: quote the xxx ?
phf: one disadvantage of irc is that once you start on a thought, you can't really revise. i didn't really have a good punch line, so i left it at that, a dud, rather than fizzle with a weak punchline.
a111: Logged on 2017-12-25 23:56 phf: so naturally i was surprised and delighted when i came to u.s., and discovered that every other person i'd meet was also russian, by way of a great great great great parent who imigrated from ireland, fleeing as he was the repercussions of second desmond rebellion
MTW: yeah that is the smart way to do it
trinque: the bot uses a cold wallet, with a human step
trinque: MTW: ah, I see it. there's a printout I apparently didn't get. give me a few and I'll dispatch.
a111: Logged on 2017-12-25 22:55 ben_vulpes: that don't touch the same file
mircea_popescu: http://btcbase.org/log/2017-12-25#1758589 << i don't get what the problem is. write a patch that modifies the filebase into the shape you want it to be. what's the problem ?
BigTexasBingo: Polishing my boots for a week of pounding pavement during the day on the isp and pounding something else in the evenings
BigTexasBingo: Muchas gracias. Navidad muy tranquila after the three solid hours of latino Xmas fireworks
phf: so naturally i was surprised and delighted when i came to u.s., and discovered that every other person i'd meet was also russian, by way of a great great great great parent who imigrated from ireland, fleeing as he was the repercussions of second desmond rebellion
phf: he said, oh yeah, so i had to explain that you could say that i was irish, by way of Rurik, who was a Varangian. when the guy finally understood what i was talking about, he was not amused, possibly because i got my nordic tribal relationships wrong
phf: so first time i got on irc, 96 or so, i was on some random irc channel, and overcome with the awesomeness (in the proper sense) of this intercontinental communication. the person i was talking to was irish, so, eager to find some common ground in this historically first teleconference between the russian people and the irish, i blurted that you could say that i'm also sort of irish
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: "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
lollig400: ▄▄▄▄▄▄▄▄▄▄▄▄ HAPPY NIGGER MAS!! IF YOU WANT JOIN A CELEBRATION THAT IS NIGGER FREE PLEASE JOIN #/JOIN RIGHT HERE ON THIS NETWORK!! elmkussi: whaack phf The20YearIRCloud asciilifeform danielpbarron ben_vulpes _whitelogger Framedragger ang-st gribble jurov shinohai mquander spyked mod6 MTW StarmanDeluxe punto yangwao_ Techman deedbot kjj dooglus mircea_popescu trinque mimisbrunnr
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.
a111: Logged on 2017-12-21 01:52 phf: i think correct method would really be to get the transaction out as a binary array into shiva, and then have a transaction parser in shiva itself that'll break it down into a sexp or whatever
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.
a111: Logged on 2017-12-25 18:32 l0de: get someone to call in and do an infomercial about the republic
mircea_popescu: and speaking of http://btcbase.org/log/2017-12-25#1758548 anyone got any ideas of how to meaningfully support the SW hobbist ?
mircea_popescu: this drives the screw into the psychopaths that their wankworld is just one random wankworld among many extant and possible ones, of no further interest than any other piece of bad fanfic, and besides, evidently the only way to satisfy c is if they conquer each other, so maybe ww-lulz can be had in the same go.
mircea_popescu: ) ; b) that the "law" of $random-other-fiatlul MAY (not does, MAY) diverge in any manner at any point and finally that c) it is incumbent on the pretender to exhaustively prove to any arbitrary standard that b does not apply.
mircea_popescu: anyway, for the record and in case it isn't entirely self-evident on the basis of http://btcbase.org/log/2017-12-25#1758486 : whenever some self-proclaimed "sovereign" of the fiat sort tries to say "hey, we have a law", the correct response is to a) point out to that self-proclaimed faux sovereign that there exist other just as valid because just as self-proclaimed faux sovereigns (the eu, russia, china, whatever, bucnha them
l0de: get someone to call in and do an infomercial about the republic
l0de: who I believe registered and leapt through the hoops
l0de: ya, he's sending the funds to MTW
l0de: fare the well, hollar @ dpb if you see him for me
l0de: alright, well I am off to take advantage of the holiday cheer by swindling some people
mircea_popescu: lol romania is rather unrelated to gypsies.
l0de: because we don't currently have a platform that can deal with them in a meaningful way
l0de: it is a huge fucking pain in the ass to deal with those
l0de: well, I would suggest you remain open to the possibility that this capability exists
mircea_popescu: they have less of an ability to impede sw comms than the soviets had in 1977 ; and it didn't work for the soviets in 1977.
l0de: why do you believe they lack that capability
mircea_popescu: they have no suych thing
l0de: to the point of unusability
l0de: at the point where shortwave communications pose an existential threat to usg
mircea_popescu: in point of fact the usg is today much less powerful or capable than ye olde ck-kpss.
mircea_popescu: the point doesn't JUST go re nukes per se ; this whole "usg could do THE BIG THING" is entirely pantsuit wank.,
mircea_popescu: i guess you can now read http://trilema.com/2015/i-think-you-drastically-overestimate-the-military-importance-of-nuclear-weapons/
l0de: because of the whole ww3 thing
mircea_popescu: render usable how, exactly ? like the soviets did ?
l0de: If shortwave was the problem, the USG could render the entire thing unusable with relatively trivial effort
mircea_popescu: the idea isn't at any point to somehow "appear small and escape detection".
mircea_popescu: this is rather an advantage.
l0de: every single thing happening on shortwave is of interest to them
mircea_popescu: as far as mostly 1 is concerned, there's significant interest in shortwave, which is why it's a recurrent thread in the logs.