mircea_popescu: trinque kitten trying to get into the backseat so i can play with her tits ever so briefly kissed my new suit pant's leg, now i have a typically indicative white spot on it. tbh i knida like the look of it.

mircea_popescu: anyway, and the proposed fix for this is to actually add a hash for the whole filebase in each patch ?

mircea_popescu: hey, i spent most of the intervening day revelring! i have circumstrances!

mircea_popescu: because otherwise, touching entirely different filesets, their precedence can not currently be established as per extant v

mircea_popescu: the ~only way to establish a lineage among these two so a3` is properly a4 is if the patch is spuriously modified to add a "hey v sucks" comment in Fj

mircea_popescu: so the idea is, you got up to a2, which consists of files F1... Fi ; now one patch call it a3 touches file Fj, and another patch call it a3` touches file Fk

mircea_popescu: ben_vulpes oh it finally dawned on me what this is about. sorry it takes so long.

mircea_popescu: ok

mircea_popescu: it doesn't matter which files they touch. a4 will build upon one of them, and then a5 on a4, and the unbuild upon one is left as a "fray" on the rope.

mircea_popescu: there's still a disconnect because i don't understand what the hell you mean.

mircea_popescu: (this results in an immediate reimplementation of eg's linus torvald's linux codebase management, except properly and per protocol rather than ad-hoc and in a manner nobody can explain or meaningfully defend)

mircea_popescu: because the tree will continue and NOT upon it.

mircea_popescu: if the patch tree goes a1->a2->a3/a3` your position is now to choose which of a3 or a3` counts, and which doesn't count. the discarded one may be scavenged for useful content, but it will never be a proper patch.

mircea_popescu: http://btcbase.org/log/2017-12-27#1758965 << this is exactly what's discussed in http://btcbase.org/log/2017-12-26#1758702 : only way to recover code in a heretic patch (ie, one you're not pressing upon) is to literally lift it and include it. ☝︎☝︎

mircea_popescu: trinque there's an ambiguity here i'm possibly responsible for though not intended : to "regrind", ie to take a pile of patches and make them into one single patch ; as opposed to re-genesis, which is what happened with eg mpi.

mircea_popescu: whereas the pantsuit psychotic cleaving, where ~some kinds~ of spam are spam (ostensibly because they came from russian hackers as per their bayesian filters ?) whereas some other kinds of spam magicaloly "aren't spam" somehow, because pravda said it, or some "transgender" schmuck said it, or whatever.

mircea_popescu: somehow the voice model makes spam such a rarity in #trilema, people actually have the mental vigour to evaluate it!

mircea_popescu: so on. because "it's spam" and that means "it shouldn't be read" and they actually have a consensus on this, which they idiotically but universally misrepresent as somehow different from any other cultish behaviour, such as believing "racism" or "global warming" or "witchcraft" are things.

mircea_popescu: and in unrelated lets-suck-our-own-cocks-we-utterly-deserve-it : consider that the whole l0de thing started because someone from here checked out a SPAMMED item. the fuctard/pantsuit "engineers" in name only in EVERY OTHER fucking channel ~think~ themselves all open-minded and intelligent and whatever, yet i can make a very obviously correct and banal prediction - they wouldn't have followed it, nor in any case escalated and

mircea_popescu: because why.

mircea_popescu: trinque which is a valid thing to do, but NOT if one wishes to at the same timeeschew regrinding/genesising

mircea_popescu: http://btcbase.org/log/2017-12-27#1759045 << correct, misspelled. ☝︎

mircea_popescu: is there a different reason ?

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: is this contentious ?

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.

mircea_popescu: now suppose lord Y comes along, and similarily makes B : B1->B2->B3->B4.

mircea_popescu: so suppose lord X makes tree A : A1->A2->A3->A4 are patches, delivering some kind of utility we don't care to specify.

mircea_popescu: let's make a working model here.

mircea_popescu: why not ?

mircea_popescu: in preference of regrinding the item ?

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 ☝︎

mircea_popescu: trinque do you sign it ?

mircea_popescu: specifically "do a good job in preference of a bad job, last longer".

mircea_popescu: a lesson for all future minds in there.

mircea_popescu: as history ended up unfurling, "let's truncate hash to 10 chars or 20 chars depending" takes one from 2009 to some portion of 2018. better than nothing ; much less than could have been had, if only.

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.

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

mircea_popescu: under the authority of the republic ; not trying to enact selves out of the well threadbare wizard cloak of satoshi.

mircea_popescu: asciilifeform i intend to prove no such thing to no such martian.

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.

mircea_popescu: ie, i don't expect the trb cut as described to have a trb genesis necessariyl, or even probably.

mircea_popescu: it's after all what diana_coman is doing for eulora.

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.

mircea_popescu: ie it takes a major regrind ?

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".

mircea_popescu: now, is this enforcement a problem with v, is the proposition ? or is the aforegoing a misrepresentation of the discussion ?

mircea_popescu: v doesn't permit this backwards in time ; and if you run in this situation where johnny needs an experts' sex change to become evvie, it's high fucking time you hand-rewrote your whole steaming pile of crap.

mircea_popescu: s hack it backwards in time".

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: and how can one not modularize ?

mircea_popescu: http://btcbase.org/log/2017-12-27#1758945 << explain what modularize means here ? ☝︎

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.

mircea_popescu: 20bux in the chinoshop

mircea_popescu: damned thing was the size of a god damned depth charge

mircea_popescu: anyway, personally launched lb+ "polvoras" ie fireworks here.

mircea_popescu: BingoBoingo ftr, .6 out of 1.3 is more like 45^

mircea_popescu: take it ezzy.

mircea_popescu: a sense of confort, the common woman's mindeater.

mircea_popescu: if you register a key you can self-voice don't have to keep doing this voicing thing

mircea_popescu: !!key l0de

mircea_popescu: !!up l0de

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 ☝︎☟︎

mircea_popescu: http://btcbase.org/log/2017-12-27#1758894 << portobello not pleurotus anyway. ☝︎

mircea_popescu: http://btcbase.org/log/2017-12-27#1758883 << sure. in the sense blockchain is frayed rope, this also. ☝︎☟︎

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. ☝︎☟︎

mircea_popescu: http://btcbase.org/log/2017-12-27#1758859 << gotta get SOME filtering process in place though ☝︎

mircea_popescu: if we had a chinese girl that'd work, except, of course...

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: http://btcbase.org/log/2017-12-26#1758815 << do it in castellan, maximum lulz. ☝︎

mircea_popescu: http://btcbase.org/log/2017-12-26#1758811 << how's danielpbarron 's radio voice ? ☝︎

mircea_popescu: basically something like "do x, get y" with a well chosen x. ☟︎

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. ☟︎

mircea_popescu: http://btcbase.org/log/2017-12-26#1758800 << this was re http://btcbase.org/log/2017-12-25#1758556 ☝︎☝︎

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" ☝︎☟︎

mircea_popescu: http://btcbase.org/log/2017-12-26#1758784 << true. ☝︎

mircea_popescu: phf word.

mircea_popescu: then if it is, trinque's point goes away because well... file hash as good as project hash for the linear bat.

mircea_popescu: imo "tree" MUST be linear. ☟︎

mircea_popescu: trinque this is actually not altogether a meritless point.

mircea_popescu just dumped a whole sack of coal on teh grill, teh girls happily cleanning up a grosse of pleurotus... if anyone needs me ima be at teh rancho bbqing. ☟︎

mircea_popescu: lel

mircea_popescu: why so hostile anyway bb ?

mircea_popescu: go make yer castles today, so noobs have a shot at life in 2018 ☟︎

mircea_popescu: more practically, voice will be acquired via introduction by lord, ie, court presentation. ☟︎

mircea_popescu: "avoidant" as per teh "attachment theory" nonsense that pantsuit "public policy" rests upon

mircea_popescu: phf it is, isn't it ?

mircea_popescu can't recall if mp-wp still supports psql or not

mircea_popescu: might need mysql db installed separately if only comes with postgres or something

mircea_popescu: atm some apache, but historically also nginx