log☇︎
110400+ entries in 0.038s
asciilifeform: in this system.
asciilifeform: i can still make you a cycle.
asciilifeform: if you formalize this -- we can work from that.
asciilifeform: (to produce what? patches of patches ?)
asciilifeform: you will need to describe a v-prime where patches get diffed
asciilifeform: nobody's diffing the patches, mircea_popescu
asciilifeform: nobody's hashing ~the patches~. mircea_popescu wants to ?
asciilifeform: of the patch..?
asciilifeform: in both
asciilifeform: --- a/foo.txt 74e20d520ba4ecfdb59d98ac213deccecf591c9c6bfc5996ac158ab6facd6611cce7dd22120b63ebe9217f159506f352ce0ee6c0c2a1d200841ae21635dc5f9a
asciilifeform: it is already in
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: (this in my original example.)
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.
asciilifeform: this was quite apparent from my paste.
asciilifeform: a and b are on separate planets , and do not know about each other, and each was working from the genesis only.
asciilifeform: which it does not
asciilifeform: you made b1 depend on a1
asciilifeform reads
asciilifeform: show me what 'correctly reference their antecedent hashes' would look like.
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.
asciilifeform: http://wotpaste.cascadianhacker.com/pastes/F4SWa/?raw=true << another example of convergence
asciilifeform: for ze well-ordered record!
asciilifeform: plz
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.
asciilifeform: what of it
asciilifeform: just as bitcoin will still work when we rebake it with old balances and new clockwork.
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.
asciilifeform: there is no squaring for this circle, mircea_popescu .
asciilifeform: you cannot prevent the identical bitstrings, regardless of what epicycles you come up with. other than by ordering.
asciilifeform: martians make a copy of mircea_popescu ! which mircea_popescu shoots which other !
asciilifeform: they are the same bits ! you cannot 'choose 1'
asciilifeform: UNLESS we have clock.
asciilifeform: which takes you to the same place.
asciilifeform: i.e. identical patch.
asciilifeform: +Foo Genesis, modified.
asciilifeform: +#Patch for 53fedeea28a5b6608b422f90f8c28e97c4604d6da5c18b8167b10c994166d8f0b47cd07bca8a6e4e53b6a961bef75f494c70e97437b7afd2d69c4110d7c06575
asciilifeform: -Foo Genesis, virginal.
asciilifeform: -#Patch for genesis.
asciilifeform: @@ -2 +2 @@
asciilifeform: 25ce1cf14a94791ca4d0187cbc4247408cbc0c088dff1f13b312dff1d71af6b260d76a4df1277b66ed683dedc02852cbb3f366502459941f5e09e4594e733ac6
asciilifeform: +++ b/foo.txt
asciilifeform: --- a/foo.txt 53fedeea28a5b6608b422f90f8c28e97c4604d6da5c18b8167b10c994166d8f0b47cd07bca8a6e4e53b6a961bef75f494c70e97437b7afd2d69c4110d7c06575
asciilifeform: diff -uNr a/foo.txt b/foo.txt
asciilifeform: it does not in point of fact have a unique 'last patch applied', because there is no way to prevent two people who do not know about one another from both writing :
asciilifeform: for starters, a patch can antecedentize 10,001 other patches.
asciilifeform: what does the string 'Patch for genesis' do in mircea_popescu's paste example ?
asciilifeform: mircea_popescu: as i understand, your solution to cycles is to demand that no two patches be equal.
asciilifeform: the inequality can only be enforced by an outside synchronizer.
asciilifeform: which is same problem as in ordinary v.
asciilifeform: they will if the payload is the same.
asciilifeform: that orders for us.
asciilifeform: or to have an oracle.
asciilifeform: in order to never do this, we have to confer.
asciilifeform: and so we're nailed.
asciilifeform: we at the same time write '#Patch bfffhlerghhl' for our gensyms.
asciilifeform: and at the same time, mircea_popescu also does.
asciilifeform: say i sit down to write a patch.
asciilifeform: let's work this out :
asciilifeform: there is no concept of 'previous' without a time order !
asciilifeform: a gensym, in case anyone forgot, is defined as a symbol that is guaranteed to be unequal to all other invocations of gensym.
asciilifeform: this still requires ordering.
asciilifeform: mircea_popescu's solution, if i understand it, is to include a gensym in each patch body.
asciilifeform: and you want to find out ~who~
asciilifeform: what you need ordering for is if someone ~does~ break the no-old-antecedent-hashes-as-descendants rule
asciilifeform: in mircea_popescu's paste, there is only 1 way.
asciilifeform: to have concept of 'new' and 'old'.
asciilifeform: which still requires ordering.
asciilifeform: you can ban it, as shown above in mircea_popescu's paste, by demanding that no new patch produce the antecedent of an old one.
asciilifeform: sure we can. at least under my original vtron, this was a legal operation because it does not produce an eternal walk.
asciilifeform: mircea_popescu: this destroys the ability to see that we in fact returned to genesis. has it occurred to you to wonder why even to have patches at all? why not everyone just signs the entire hindenburg titanic of trb every time he changes a line ?!
asciilifeform: mod6's vtron, in this respect, worx.
asciilifeform: it stopped at genesis.
asciilifeform: correct.
asciilifeform: nah
asciilifeform: mod6: now try to get antecedents for foo-modified
asciilifeform: which is correct.
asciilifeform: and you can prove that it will.
asciilifeform: the alarm -- rings.
asciilifeform: and there is no confusion.
asciilifeform: we hash correctly.
asciilifeform: http://wotpaste.cascadianhacker.com/pastes/TwMUZ/?raw=true << this sets off the alarm.
asciilifeform: i will post it, because i have it handy
asciilifeform: yours rings the alarm bell.
asciilifeform: it is legal in my vtron, because it 'returns to earth'
asciilifeform: cum genesis.
asciilifeform: mircea_popescu: http://wotpaste.cascadianhacker.com/pastes/VZVHu/?raw=true << here is your 'cyclic ring of 3 atoms'
asciilifeform: there is no colour of bits.
asciilifeform: davout: those are the same thing
asciilifeform: (this was an aesthetic choice of mine, it can be revoked quite simply)
asciilifeform: returning to genesis is permitted, because the toposort still terminates.
asciilifeform: note that a correct vtron will not misbehave if you have this.
asciilifeform: -Foo Genesis, virginal.