log☇︎
229800+ entries in 0.06s
asciilifeform: what recovery can there be, when your $maxint coins walk away?
asciilifeform: nor have any reason to place trust in the creators
asciilifeform: i won't use, because i was not privvy to the process whereby it was born.
asciilifeform: ben_vulpes: no.
asciilifeform: (well - at least, i'm not)
asciilifeform: why aren't we using them?
asciilifeform: and 2 or 3 others.
asciilifeform: conformal corp.'s reimplementation exists, for instance.
asciilifeform: two separate problems.
asciilifeform: and then how to convince others you are not a martian ?
asciilifeform: aha but how to observe?
asciilifeform: i hear it's popular.
asciilifeform: that's an option.
asciilifeform: and the only way to learn it, is by their works.
asciilifeform: we want to know, even if it is fifty years too late, who they were.
asciilifeform: but we do know that among us are hostile martians, who would like us to come to harm.
asciilifeform: we have no idea, let's say, what parts are useful, and which ones are boobytraps designed to kill unwary earthling dissector.
asciilifeform: let's pretend that it just happened to fall upon the earth. ☟︎
asciilifeform: undata: picture the 0.5.3 turd as a piece of martian technology.
asciilifeform: well, you referred to 'trustworthiness' which is a thing we have not yet invented.
asciilifeform: right now it is a null word.
asciilifeform: 'trustworthiness' can only be born from this.
asciilifeform: now, and 100 years from now.
asciilifeform: the most important thing is that each and every change, however slight, is attributable.
asciilifeform: that being - attribution.
asciilifeform: Adlai: there are two separate questions here, and we are only dealing with one
asciilifeform: lol re: linux kernel as an example to follow
asciilifeform: and requires some complicated pattern-matcher to apply
asciilifeform: but i will not be signing any patch that i can't apply with my mind, in my mental model of the code. ☟︎
asciilifeform: and whatever aspects of it can be automated - should be
asciilifeform: can't really argue that it's a great joy.
asciilifeform: it's a chore, yes
asciilifeform: no.
asciilifeform: and a dependence on the machine to resolve questions which ought to be resolved by the mind, and thus kept 'light weight' enough to be easily resolved by the mind.
asciilifeform: but the argument here is not about sabotaged ken-thompson-style tools. but about tools that foster intellectual atrophy. ☟︎
asciilifeform: (less easy to test if it is -capable- of lying, but that's another matter)
asciilifeform: it is very easy to test if my text editor is lying.
asciilifeform: idea is not 'which was diddled' but which one encourages reliance on greater and greater machine 'intelligence'
asciilifeform: software is helping to the extent it is reasonable. for instance, i am trusting my text editor to display the actual source and not some diddled version.
asciilifeform: and whiners who complain that this is arduous, unreasonable, etc. - are shown where the door is.
asciilifeform: this is how safety-critical systems work. ☟︎
asciilifeform: all three - answer with their lives.
asciilifeform: one would read instructions. another, turn a wrench, whatever. third would check that 2 corresponds to 1. then, all three sign under that step in recipe. ☟︎☟︎☟︎☟︎
asciilifeform: there was a three-man system ☟︎☟︎
asciilifeform: undata: do you know how soviet nukes and spacecraft were assembled?
asciilifeform: but don't be surprised if it is treated in the same way as the phoundation's original - at the very best, a place to steal bug fixes from.
asciilifeform: or, alternatively, create own fork, with own point...
asciilifeform: undata: if you want to understand the whole point of the fork, try to understand what you lose when you choose a vcs as a canonical representation.
asciilifeform isn't either
asciilifeform: ben_vulpes, the one fellow who is really still working on this gizmo, is
asciilifeform: undata: you are perfectly welcome to use a vcs of whatever flavour appeals to you
asciilifeform: but i will only sign deltas which consist of information which i can fully view.
asciilifeform: it's bad enough that we are dealing with a turd that is quite impossible to fully understand in the original.
asciilifeform: let's put it another way. i will not sign anything that i cannot read.
asciilifeform: others can disagree, and sign the empire state building.
asciilifeform: but it is that output, and only that, which i am willing to sign.
asciilifeform: undata: well, to the extent that any version control system can be cudgelled into coughing up output compatible with 'patch' - then yes.
asciilifeform: how much of what is on your computer right now, actually -does- something ?
asciilifeform: dwarfing the actual healthy tissue.
asciilifeform: and since it never quite succumbs to the cancer, the tumours become planetary-sized.
asciilifeform: it gets cancer.
asciilifeform: look at extant software and you will see what happens to engineering when moving parts stop having weight and cost.
asciilifeform: as in, cruft.
asciilifeform: but -things-.
asciilifeform: the point here is not to filter undesirable -people-
asciilifeform: this business, where things have to keep 'growing' for no apparent reason at all, needs to go.
asciilifeform: http://esr.ibiblio.org/?p=6271
asciilifeform: incidentally, esr had a piece on it.
asciilifeform: undata, Adlai: are you familiar with 'risk homeostasis' ?
asciilifeform: undata: i want it to get harder.
asciilifeform: try to understand the nature of this 'nuke sub' and the pitfalls of tying one's fortune to 'darcs' or a similarly 'intelligent' instrument.
asciilifeform: *filename
asciilifeform: Adlai: we have the metadata. the integer in the patch fileames.
asciilifeform: (if you have a solution, geneticists would love to hear about it. 'sequence alignment' is ruinously expensive, in computational terms.)
asciilifeform: incidentally, the problem of 'patcher than is never fooled by deletions and line count shifts' is not solvable in the general case.
asciilifeform: Adlai: does it, for example, avoid being fooled by line number counts?
asciilifeform: Adlai: in what way is 'darcs' output more useful than unix patch?
asciilifeform: and per the current state of the art, that means unix diff outputs.
asciilifeform: but when it's time to cough your changes back up and have them up for public study, they have to be physically minimal
asciilifeform: (the canonical representation can be taken and stuffed into a git repo, or darcs, or cvs, whatever, for your personal pleasure)
asciilifeform: try to understand why a git repo cannot be the canonical representation.
asciilifeform: aha i think ben_vulpes has one of his own
asciilifeform: for reasons described earlier.
asciilifeform: but it is only a tool that some people prefer to use. a 'git' or other similar gizmo will not be the authoritative representation of bitcoind.
asciilifeform: it even, iirc, comes with a gpg signing gizmo
asciilifeform: Adlai: on the contrary, several people (even you?) are using 'git'
asciilifeform: i know i like to.
asciilifeform: i guess there's something pleasurable in seeing the moduli
asciilifeform l0lz that folks are using 'phuctor' as a key viewer
asciilifeform: (only updates when someone craps a key in)
asciilifeform: lol wasn't meant to be used as an authoritative keyserver.
asciilifeform: 'Who steals my purse steals trash; 'tis something, nothing; 'Twas mine, 'tis his, and has been slave to thousands; But he that filches from me my good name...'
asciilifeform: the abuser.
asciilifeform: get a hammer, leave microscope alone.
asciilifeform: but still why.
asciilifeform: well yes.
asciilifeform: but why?
asciilifeform: one could in principle maintain a bitcoin 'keypair' for the purpose of abusing it for public key signatures
asciilifeform: whether this particular microscope is fit for use as a hammer, depends on two very separate questions - what you think of ecdsa, and what you think of bitcoind
asciilifeform: ( http://www.motherjones.com/politics/1996/07/cyberselfish << briefly described here.)