log
262 entries in 0.599s
phf: well, presumably all this only applies when you have fits in head. otherwise you have to fallback to counterparty
phf: we were comming from the direction of debian on 10 cds though, so restating my original point: i think bootstrapping can be solved with counterparty as an alternative to fits in head, i.e. i don't mind an approach where in order to bootstrap i get a binary from l1, that i use as a rich subtrate from which i can bootstrap.
phf: i think i see why we got on this thread. i was saying that bootstrapping is always a counterparty problem. i missed that that's not the case for fits in head (i think ascii might've tried pointing that out to me).
asciilifeform: not quite 'fits in head' machine, but 'fits in book'
asciilifeform: trinque: there is no tangle properly speaking ~in~ their skull. when proggy no longer fits in head, programming turns into a brute physical, rather than intellectual activity
a111: Logged on 2017-02-11 00:27 asciilifeform: ROP is why you want not only 'fits-in-head' source of proggy, but the smallest binary physically possible.
asciilifeform: ROP is why you want not only 'fits-in-head' source of proggy, but the smallest binary physically possible. ☟︎
asciilifeform: and the only countermeasure is to keep the changes to grandfather's pistol, minimal, reviewable, 'fits in head.' and to retain old mechanisms when practical.
asciilifeform: is in no real 1980s sense 'fits in head'
ben_vulpes: the situation's a good example of the tension between writing code that does one thing really specifically well, and fits-in-head, vs a larger program that handles eg conditions and the concomittant complexity
phf: metafont fits in head
asciilifeform: it isn't even about 'attack surfaces', but for getting maximally compact description. i.e. fits-in-head.
a111: Logged on 2016-09-17 04:18 adlai has been reviewing math towards next month's semester start. just encountered a beautiful "fits in head" derivation: https://en.wikipedia.org/wiki/File:AngleAdditionDiagramSine.svg
adlai has been reviewing math towards next month's semester start. just encountered a beautiful "fits in head" derivation: https://en.wikipedia.org/wiki/File:AngleAdditionDiagramSine.svg
asciilifeform: the sleep of fits-in-head breeds monsters.
mircea_popescu: check him out, adept of fits in head, worried about not being able to find the broken code HE SHOULDNT HAVE HAD. pshhh
asciilifeform: let's revisit thread - what part of 'fits in head, and speccable, or doesn't-fit-in-head, unspeccable, t. non d.' does mircea_popescu disagree with ?
scriba: Logged on 2016-09-13: [17:51:53] <asciilifeform> the reason why we ~have~ spec-by-program is because it is the only actual alternative to fits-in-head.
asciilifeform: the reason why we ~have~ spec-by-program is because it is the only actual alternative to fits-in-head.
asciilifeform: and not fits-in-head.
asciilifeform: but 'fits in head, except for this massive part that presently fits in no head' is not same as 'fits in head'
asciilifeform: g_l: really now, fits in head, incl. the font engine crap etc. ?
g_l: http://btcbase.org/log/2016-08-30#1531840 < CLIM fits-in-head, and the final showstopping error (X11 related crap) has been reduced to a simple test case, and is in the process of being solved. ☝︎
asciilifeform: (for which the toolkit includes, e.g., 'fits-in-head')
phf: it doesn't satisfy our own requirements of fits in head, it goes through a rube goldberg machine in order to produce a specific build for a specific system. "mac os x? fuck you. openbsd? fuck you". it doesn't succeed at own goal of producing bit identical builds.
ben_vulpes: but the notion of a "fits in head" ethereum contract boggles the mind, so.
asciilifeform: the correct answer, from the twin standpoints of reliability and fits-in-head - is bitcoinfs.
asciilifeform: mircea_popescu: fits-in-head means that i get to huffmanize TO THE MAX
mircea_popescu: omfg what the fuck do you think "fits in head" means.
asciilifeform: which is a fallacy because... correct-c still is not conducive to fits-in-head; is not readily distinguishable by naked eye from underhanded-c; cannot provide rational guarantees of handling error conditions mid-way; and 10,001 other defects that don't look like defects to folks who grew up with crippled systems
a111: 80 results for "fits in head", http://btcbase.org/log-search?q=fits%20in%20head
asciilifeform: $s fits in head
mod6: I'm a bit hesitant to "sign" a file outright that I don't have carnal knowledge of -- say openssl - at least without a disclaimer that says "I am only confirming the SHA512 of this artifact is ABCDEF1234... This does not mean that I have read that code and it ``fits in head''."
a111: Logged on 2016-06-19 03:45 asciilifeform: which is to say, the tokamak folks are about as interested in desktop, $1000 fusion (of ~whatever temperatures~) as the maths dept at your uni is interested in elementary proof of fermat, or the software 'industry' - in 'fits in head', etc.
asciilifeform: which is to say, the tokamak folks are about as interested in desktop, $1000 fusion (of ~whatever temperatures~) as the maths dept at your uni is interested in elementary proof of fermat, or the software 'industry' - in 'fits in head', etc. ☟︎
asciilifeform: a fits-in-head library with no loose parts and no sharp edges can be used as it is.
trinque: and thus entirely not "fits in head"
trinque: doesn't this run directly against your fits-in-head thing?
mircea_popescu: science as "fits in head" is not exactly practicable anymore.
phf: flask is not standalone though, it's a wsgi service, which in turn is a python standard for doing "web application". there are competing servers for wsgi, uwsgi being most popular. i actually had to patch it for my work production, and it's not a fits in head by any means
asciilifeform: where he 'fits in head'.
phf: exponent fits in head
asciilifeform: 1.1MB TGZ of src !11 this does not appear to be in any serious way 'lighter' or more fits-in-head-sy than x11.
asciilifeform: mircea_popescu: in the interest of fits-in-head - sure
mircea_popescu: this is WHY your "fits in head", btw. well justified cover for the "on the basis of the pi we know, the largest house that can stand is 11 feet tall"
adlai: 'fits in head' has another interpretation.
davout: anyway, my point is that if nobody remembers, that nobody bothered to blog it, the fact that completeness is a problem might indicate a violation of fits-in-head
asciilifeform: because 'correct' MEANS, among ither things, fits-in-head.
thestringpuller: asciilifeform: when I hear "fits in head" >> http://cdn2.thegloss.com/wp-content/uploads/2015/11/Knowledge.gif
mircea_popescu: within "minutes", where "minutes" just neatly fits in the cartel head-of-best-chain report delay.
asciilifeform: minimal as specified in r5, AND ts does not fully implement r5 (largely in the interest of fits-in-head, but also original author's laziness)
mircea_popescu: forget fits in head, this doesn't even fit in ass.
asciilifeform: tinyscheme fits in head.
asciilifeform: remember 'fits in head' ?
asciilifeform: it intereferes with fits-in-head and therefore harmful.
asciilifeform: what i wanted was a generic, fits-in-head (a few 1000 lines of c, no deps) stateless, 'protocol-less' cipherator that one could put, e.g., ftp over
punkman: "because why trust on a single cryptographic primitive" << because it's nice if the whole thing fits-in-head, and even if you cascade there is still the possibility of meet-me-in-the-middle attacks or I dunno what else
asciilifeform: k's essay was really about 'fits in head'
ascii_butugychag: http://log.bitcoin-assets.com/?date=04-02-2016#1396374 << sorta what bernstein tried to do. fits-in-head ciphers. ☝︎
assbot: Logged on 04-02-2016 15:56:22; ascii_butugychag: punkman: fits-in-head only plox.
BingoBoingo: fits in tweet no guarantee of fits in head, head can overflow buffer and leak memory too
ascii_butugychag: punkman: fits-in-head only plox. ☟︎
thestringpuller: the rule of thumb "fits in head" helps with the notion of owning device which when understood could "fit in head".
mod6: As soon as we have our new build process in place, and it's sane, and "Works" and "fits in head" and all that, then we'll release.
thestringpuller: can't imagine 1mb vpatch that "fits in head"
mircea_popescu: asciilifeform actually may want to write him a letter, iirc he was also all about fits in head but arrived there on slightly different path
ascii_butugychag: 1) fits-in-head. also known popularly as 'knowing precisely wtf you're doing'
BingoBoingo: whitespace is all about fits in eyes, not head
asciilifeform: and also don't wait for me to write a fits-in-head and provably non-misbehaving btc client, even though i would much like to, know exactly how, and even have bits'n'pieces sitting around. because instead of this i'm stuck doing pointless crud in шарашка, so as to eat.
assbot: Logged on 12-01-2016 20:57:40; trinque: mircea_popescu │ http://log.bitcoin-assets.com/?date=12-01-2016#1367833 << i can't discern which side you're taking. << the side with mostly (if not *entirely*) plain english, and even better, represented as an explicit tree with s-expressions. that one can parse the hieroglyphs when he's habituated to them... fine, but I thought we were after "fits in head" here. how much skull-space does that
trinque: mircea_popescu │ http://log.bitcoin-assets.com/?date=12-01-2016#1367833 << i can't discern which side you're taking. << the side with mostly (if not *entirely*) plain english, and even better, represented as an explicit tree with s-expressions. that one can parse the hieroglyphs when he's habituated to them... fine, but I thought we were after "fits in head" here. how much skull-space does that ☝︎☟︎
mircea_popescu: <BingoBoingo> RSA offers a longer hisotry of being studied and attacked << more importantly, it actually fits in head. a 12 yo's head.
asciilifeform: there is such a thing as fits-in-head
phf: so what do you do when not everything fits in head?
BingoBoingo: <jurov> whether "stratum" protocol fits in head for easy control, that's another question. << A lot of this. I'm imagining and "electrum" that isn't actually electrum. i.e. not a big ball of whatever that desperately wants to advertise to the world exactly what it is. basically a different better database client setup. May break down and learn to make code enough to shit one out by 2030.
jurov: whether "stratum" protocol fits in head for easy control, that's another question.
phf: in 60 years will be using "f", a fits in head filesystem implementation by ascii, that can store terabytes of data, but technically indistinguishable from tape archive
asciilifeform: the old saw, 'you own only what fits in one hand while firing with the other' is not applicable if using two-handed weapon. because then, you own only what fits in head (and arse...)
mircea_popescu: fits in head, i suspect, is just your bait and switch to make the world "fits in ass".
ascii_field: it is important to remember why we came up with the whole shebang of 'fits-in-head 1-page' patches, 'v', the lot
ascii_field: understand, i have no objection to tools such as computerized theorem-proving, data flow analysis, etc. except in that these are put forward as ~substitutes for fits-in-head simplicity~.
ascii_field: my other problem is that i have not yet found an implementation of ml language that fits-in-head.
ascii_field: from usg's point of view, ANYTHING is better than having folks wake up to cpu-with-bounds-checking-on-all-ops and fits-in-head
ascii_field: invariably subtracts from fits-in-head.
asciilifeform: it is important to know why items such as picolisp and mulisp exist - compactness. (and to a lesser extent, 'fits in head'.)
pete_dushenski: university was 'fits in head'
assbot: Logged on 09-09-2015 11:39:38; asciilifeform: http://log.bitcoin-assets.com/?date=09-09-2015#1267236 << the path to fits-in-head STRICTLY depends on every particular thing on the machine being implemented ONCE. this includes lexer, parser, related items.
asciilifeform: http://log.bitcoin-assets.com/?date=09-09-2015#1267236 << the path to fits-in-head STRICTLY depends on every particular thing on the machine being implemented ONCE. this includes lexer, parser, related items. ☝︎☟︎
asciilifeform: this means fits-in-head.
ben_vulpes: "fits in head" is a realistic goal with python, perl and cpp?
mircea_popescu: fits in head
mircea_popescu: <trinque> really illustrates your "fits in head" << i've seen his codework before and was very pleasantly impressed.
trinque: really illustrates your "fits in head"
ascii_field: mats: i have often named historical examples of 'fits in head.' but you choose to ignore them. why ?
mats: and then there's the much less measurable thing i presume you're talking about, which is those leaks that result from 'fits in head'
asciilifeform has very little patience for peddlers of 'hardenings,' 'mitigations,' and other so-called 'solutions' which are guaranteed to advance the pestilence of non-fits-in-head
mircea_popescu: "fits in head" too ?
asciilifeform: the ultimate systemic solution is 'fits-in-head'
asciilifeform: seems as if they are even abolishing 'busybox' in favour of something 'fits-in-head'-flavoured
asciilifeform: the book (lovingly referred to as sicp, 'sick pee') is a textbook illustration of precisely what i mean when i say 'fits in head'.