log☇︎
231200+ entries in 0.201s
asciilifeform: you are permitted to go to the same place via 2+ paths, because the graph is mandatorily acyclic and directional.
asciilifeform: because in the extant scheme, 'a == a'.
mircea_popescu: asciilifeform so this makes it a uniquely poor example, seeing how it will conceivably sink the extant scheme.
mircea_popescu: if a and b are conflictors then the resolution of their differences will be in either a or b tree ; importing code from either b or a respectively to satisfy ; and the other branch may die.
asciilifeform: we do not have any merged-conflictors on that graph, universe is not yet old enough for this headache to have occurred naturally
mircea_popescu: much like currently mod6's latest, the makefiles patch. takes 'mod6_der_high_low_s' , 'malleus_mikehearnificarum', and 'asciilifeform_maxint_locks_corrected' .
mircea_popescu: but this does not prevent c from calling both of them, does it ?
asciilifeform: and there is no way to erase this fact.
asciilifeform: mircea_popescu: with your algo, 'a' cannot produce the same thing as 'b', because their immediate antecedents were different.
asciilifeform: say 'a' and 'b', after futile period of divergence, have decided to produce a common offspring 'c'. what does c look like ?
mircea_popescu: maybe we're not talking of the same thing, but isn't the very patch in question, with its 3 references, a converger ?
asciilifeform: draw for me the converger plox
mircea_popescu: anyway - so you list all 3 if there's 3. fine. why does this make convergence impossible ?
asciilifeform: which one to behead ?
asciilifeform: two d00dz simultaneously (as far as we know) shoot out (b)s that make cycle.
mircea_popescu: yes, but this time a clock is no longer necessary for the beheadings.
asciilifeform: if you want to absolutely ban cycles, mechanistically, you are stuck with (a)
asciilifeform: mircea_popescu: if (b) is available, it becomes again possible to close cycles.
a111: Logged on 2016-12-23 19:26 mircea_popescu: there's multiple approaches available. a) each patch nails down the whole list of direct antecedents, so it'd be 3 in this case ; b) each patch signer picks an arbitrary antecedent to reference of the list (of here - 3), others are free to "fork" it by picking a different one or w/e.
asciilifeform: which imho is a terrible place to end up in voluntarily.
asciilifeform: it begins to resemble the popular picture of time travel.
asciilifeform: and if any two descendants pick variant paths, they create that many paths again ~squared~, and so on.
asciilifeform: because every descendant would be stuck having to pick, arbitrarily, one or the other path. and so on for ~each~ junction where this happened.
asciilifeform: even if it wants to.
asciilifeform: mircea_popescu: if your branches cannot converge (and under your algo, they cannot, because path dependence ~everywhere~) your tree gets cancer, every single patch creates a wholly separate universe that can never touch others.
mircea_popescu: the next day, bee dog saw a duck. because it wasn't blue therefore it was white and because it didn't have arms it therefore had claws and the bee dog ran back to town and warned everyone of the white wolf
mircea_popescu: according to similar legend, there was once a bee dog who saw a glass bottle. because it wasn't red it therefore was grey and because it wasn't fleecy it therefopre was toothy and so the bee dog ran to town and warned everyone of the wolf.
asciilifeform: this ~is~ a solution to 'i never again want to lose the key'
asciilifeform: according to legend, once upon a time, long ago, mircea_popescu lost his house key. so the next day he ordered twenty wagons of glue, and glued everything together -- the gurlz, the keys, his keyboard, his chair, ...
mircea_popescu: i also dun get such grumbles ? apparently there's a lot of divergence to be discussed here lol.
asciilifeform: and asciilifeform doesn't even sit in trb-foundation!
asciilifeform: i already get grumbles that trb is an asciilifeform-vertical.
mircea_popescu: well i dunno, the idea of code kinda is to be massive verticals. it;s unclear to me whence this "Signing entire project" comes from either.
asciilifeform: which is same as not even using v at all, but signing the entire project again and again.
mircea_popescu: i don't see this impossibility you discuss.
mircea_popescu: there's multiple approaches available. a) each patch nails down the whole list of direct antecedents, so it'd be 3 in this case ; b) each patch signer picks an arbitrary antecedent to reference of the list (of here - 3), others are free to "fork" it by picking a different one or w/e. ☟︎
asciilifeform: if each patch nails down an explicit 'and on top of THIS' press sequence, it drags the entire universe behind it, all of a sudden there is no such thing as 'sibling', i.e. a thing that goes from same ancestor to a different but nonconflicting place.
mircea_popescu: so what'd be the problem ?
asciilifeform: take mod6's latest, the makefiles patch.
asciilifeform: actually, strike that;
mircea_popescu: seems to me it would look exactly the same.
asciilifeform: is it even still possible to draw anything like a readable graph ? or would it look like a ball of yarn where it's this-here-copy-or-fuckyou, and it is not clear at all what was changed and what relied on what.
asciilifeform: let's consider what http://btcbase.org/patches would look like if we had been using this algo.
mircea_popescu: in any case, "-if + for" is NOT the same thing wherever it appears. even if the strings are equal.
asciilifeform: all that cannot be calculated mechanically, is, for the purpose of making a mechanism, imaginary.
mircea_popescu: the context is not imagined, but very mach part of a corrent understanding of text.
mircea_popescu: the text ; the context ; and the ownership.
asciilifeform: but the thing that makes it belong to somebody, and not some other, is the seal.
mircea_popescu: right, which is what happens here. there's no such thing as "code", but only "x's code" even the same word "for" is not the same word.
asciilifeform: so the actual bits are not in fact the same.
mircea_popescu: the same exact string, if said by me, is an idea - if said by rando, is nothing.
mircea_popescu: ie, idiots can not have ideas. no matter what they do.
mircea_popescu: in the sense contemplated in http://trilema.com/2014/pro-idiotas-which-obviously-means-people-who-have-ideas-ie-idiots/
mircea_popescu: no, my contention is that this "Sameness" is entirely illusory.
asciilifeform: so i hand-cranked the sequence using mircea_popescu's method, to agglomerate, forever, a record of the path through the tree. and he is right that this will keep the toposort from detecting a loop. but this is rather like whitening an rng, it confuses only the machine, but not the reader, who will see that the ~output~ resulting from following the path is identical.
mircea_popescu: (in this application, russel = monkey.)
mircea_popescu: so yes, monkey makes ballista, shoots man. then monkey settles down, forgets about balista for a minute, spends TWO CENTURIES trying to figure out what man had already said. a rather hollow sort of victory, at least to my eyes.
mircea_popescu: her than the obvious renounciation of the constructivist delusion.
mircea_popescu: at issue is, of course, the constructivist approach to sets ; ZFC (which is the predominant, if unexamined, contemporaneous basis for set theory) disposes with this naivity, and instead approaches the matter greek-style : all sets are "constructed" by criteria in the sense of carving subsets from the superset V (ie the v Neumann universe). it is perhaps worth noting that russel's own solution favoured ~fucking over logic~ rat
a111: Logged on 2016-12-21 19:03 mircea_popescu: should be pretty evident that a dimension defined in terms of divisibility is very fundamentally not the same thing as the latin notion of dimension-as-extensibility.
mircea_popescu: and while he's incapacitated, http://btcbase.org/log/2016-12-21#1587343 << to briefly revisit the whole "greeks were actually smarter than you" thread : naive set theory (as expoused by, say, frege) runs into a problem known as russel's paradox : should the set of sets that don't include themselves include itself ? ☝︎
mircea_popescu: !!key Tribalkiller
mircea_popescu: i am saying however it makes cycles impossible, so let's see that part.
mircea_popescu: yeah, i'm not saying this is some sort of great improvement.
asciilifeform: but now i can also make 10,000,001 paths that lead to the same press, and cannot be easily distinguished by machine. which is a headache that normal v does not suffer from.
asciilifeform: in this system.
mircea_popescu: adding the hash of the antecedent to the actual file makes that hash part of the diff of the actual file, which makes it part of the hash of the patch (ie, diff of files).
asciilifeform: if you formalize this -- we can work from that.
asciilifeform: you will need to describe a v-prime where patches get diffed
asciilifeform: nobody's diffing the patches, mircea_popescu
mircea_popescu: dude. adding it in the actual file makes it part of the diff of the patch which makes it part of the hash.
asciilifeform: nobody's hashing ~the patches~. mircea_popescu wants to ?
asciilifeform: of the patch..?
mircea_popescu: adding it in the actual file makes it part of the hash for the file.
asciilifeform: what does putting 74e20d520ba4ecfdb59d98ac213deccecf591c9c6bfc5996ac158ab6facd6611cce7dd22120b63ebe9217f159506f352ce0ee6c0c2a1d200841ae21635dc5f9a in two different places, give you ?
asciilifeform: (which is what i gather mircea_popescu intended to do in his paste)
asciilifeform: they have entirely different paths, and so making them explicitly state their path, will not save you
asciilifeform: b2 can only be applied on top of b1, and a2, similarly, on top of a1.
asciilifeform: b1 and a1 are in contradiction, you can apply one or the other to the genesis.
mircea_popescu: mk lemme restate this then!
asciilifeform: a and b are on separate planets , and do not know about each other, and each was working from the genesis only.
asciilifeform: show me what 'correctly reference their antecedent hashes' would look like.
mircea_popescu: note that "insert random garbage" has not actually been proposed as far as i know.
mircea_popescu: i have nfi what i'm looking at here ; none of them correctly reference their antecedent hashes, so it's just random garbage
asciilifeform: and that this sequence could be as long as one could possibly like, 10,001 if we like.
asciilifeform: carefully note that the patches a2 and b2 are not the same.
asciilifeform: the example i just posted involves two people, 'a' and 'b', who follow entirely different paths, come to same place, because they do not know about one another and there is no clock. now you can give them a place to put magical comment, but again they have to have a drumbeat or agreement method of one kind or another, or they can still follow this same path.
mircea_popescu: now, because of a naive "repetition creates cycles" and "index=text content" joint assumption, you automatically imagine that two people signing the same (text+context) pair would create a cycle. not anymore - the situation neatly reduces to "two people sign the same patch", ie, having multiple seals for the same patch.
mircea_popescu: mplemented as introducing a comment which references the previous item in the indexed set - but this is by no means the only, or the required, or standards-candidate implementation.
mircea_popescu: nevertheless, two different solutions have been considered. one is to attach an outside clock to the process. this has the obvious disadvantage of attaching an outside clock to the process. the other is to modify the indexing process for the set, from the current "index is hash of textual content" to a more advanced "index is hash of textual content + its context". as an exemplary poc it was proposed that this change may be i
mircea_popescu: this outlines a theoretical problem, which is present. it does not have many practical implications at the present time for purely political ("thou shalt not cycle!" is an imperative) and sociological (not that many people hammering out that many patches yet) reasons. therefore its solution is not in any sense pressing.
mircea_popescu: 1. all ordered sets will create cycles whenever the index repeats ; 2. tmsr uses ordered sets to resolve specific problems of code development ; the application is called v ; 3. for the purpose tmsr uses ordered sets for, cycles are intolerable (the turing problem resolves to "acyclic set graph" in this particular case) ; 4. there is no way to guarantee numbers do not repeat.
mircea_popescu: asciilifeform lemme state this thing from my pov for teh record here.
asciilifeform: mircea_popescu takes the patch, writes it in corpses of usg soldiers in the desert, photographers come, it is printed in every paper in the world; now -- ordered.
asciilifeform: fortunately there are other ways of unambiguous ordering for the record.
mircea_popescu: except woe, you can't make it because someone already made a patch for this block and you aren't going to see another block without a patch.
mircea_popescu: this is not true. bitcoin blocks can stop right now.
mircea_popescu: asciilifeform if you mean that you and i both sign the same patch text in the same tree context, the result here has been the very common, and very benign, MULTIPLE SEALS. which we currently have.
asciilifeform: mircea_popescu: for so long as you have the flame continuously burn, and at no point 'everyone died', it runs.
asciilifeform: all bitcoin-like systems are doomed to have vaguely same shape, just like airplanes are doomed to have wings.