log☇︎
185400+ entries in 0.057s
asciilifeform: cannot be oblivious of payload
asciilifeform: this is the objection
asciilifeform: because if we deal with the insides of any text, ever, we suddenly get line-endings and escapes and crapola
asciilifeform: IT CANNOT BE THE SAME FORMAT FOR bins and text
asciilifeform: say we ask that a file carry hash in a header.
asciilifeform: ok back to the example
asciilifeform: and various oddities not really used in modern times.
asciilifeform: terminal has state.
asciilifeform: throwing garbage into a vt100-compatible terminal breaks things for reasons that are not mysterious at all. rtfm?
asciilifeform: wai wat
asciilifeform: or with magical fairy dust.
asciilifeform: by out of band sign.
asciilifeform: aha.
asciilifeform: you will even notice that sometimes this results in a permanently b0rk3d terminal.
asciilifeform: or some other source of binaryrubbish
asciilifeform: cat /dev/random and see what you get.
asciilifeform: some codes were reserved for line feed, dinging the bell (yes), etc.
asciilifeform: ask him, not me.
asciilifeform: on the basis of the fella who build the vt100
asciilifeform: so it isn't an ascii vs utf fight
asciilifeform: btw 'binaries' are not merely 'un-ascii' but include intrinsic unprintables (control chars)
asciilifeform: (that is, unconstrained to printable chars)
asciilifeform: 2) have to represent the header differently if payload is meant to be displayable ascii, than if it is a binary
asciilifeform: 1) now i have to remove the header before hashing the payload
asciilifeform: if i want to embed hashes next to their payload, i get an explosion of complexity. because,
asciilifeform: let's work this out.
asciilifeform: aha
asciilifeform: (or how much was it.)
asciilifeform: or, on one occasion, 10MB of rng output
asciilifeform: i can (and often do) sign a tar.gz
asciilifeform: if you care what's inside, now you have to cut it
asciilifeform: because don't care what's inside
asciilifeform: can have what you want in the file
asciilifeform: why ?
asciilifeform: wai wat
asciilifeform: heptylin.
asciilifeform: propylin
asciilifeform: it'll be ethylin or somesuch
asciilifeform: soviet elephants are the biggest in the world!
asciilifeform: here already
asciilifeform doesn't typically bother to read these
asciilifeform: it isn't an article, it is cant, and this is detectable via five-second litmus of first paragraphs
asciilifeform: i have been to them. prior to their burning.
asciilifeform: diametric is an actual person i see just about every day.
asciilifeform: BingoBoingo: you may be confusing him with diametric, like mircea_popescu did on a few occasions
asciilifeform: recommended.
asciilifeform: the z80 article has spiffy photos
asciilifeform: ^ was him i think.
asciilifeform: !s from:decimation www.jameslafond.com
asciilifeform: QED.
asciilifeform: !s from:ascii_field www.jameslafond.com
asciilifeform: !s from:asciilifeform www.jameslafond.com
asciilifeform: dun think so.
asciilifeform: me??
asciilifeform: wtf inglisch speaker doesn't know this ?!!!$
asciilifeform: it's rivendell
asciilifeform: BingoBoingo: 'their elven palaces in Rivendale' << fucking illiterate
asciilifeform: netstat -a ?
asciilifeform: and this
asciilifeform: and is the only instance
asciilifeform: view process list, is it running with the args you thought you ran with ?
asciilifeform: what is in the snipped part ?
asciilifeform: in that log
asciilifeform: cazalla: i don't see any connections from other ip ?
asciilifeform: thinkaboutit
asciilifeform: cazalla: and you'll be seeing an ocean of 'ConnectInputs failed' if you're not at top block height
asciilifeform: cazalla: what are your run arguments ?
asciilifeform: and searching for docs
asciilifeform: http://log.bitcoin-assets.com/?date=15-08-2015#1239163 << i read that piece not long ago, while contemplating buying one. ☝︎
asciilifeform bbl
asciilifeform: mod6: spiffy
asciilifeform: like graveworms
asciilifeform: but they devour everything
asciilifeform: then - marketards got to it, aha.
asciilifeform: originally well-defined, in the 'theory of edge wave' paper
asciilifeform: individually - one? sure. while exacerbating the others.
asciilifeform: in that aficionados will point to a list of fairly specific, supposedly-'we're almost there' problems, that in point of fact no one knows how to solve ~~in ensemble~~
asciilifeform: mircea_popescu: prolly better comparison is hot fusion
asciilifeform: like airplane in 1880
asciilifeform: they are speaking of a particular machine, which no one (as publicly known has built), but, e.g., 'd-wave' fraudulently sold to a few rich schmucks, and the difficulties of construction are not mysterious
asciilifeform: in 'lectures on computation' (r. f.)
asciilifeform: don't misunderstand, defined in strictly gedankenexperiment terms
asciilifeform: what will or will not run, is also not completely empty field (e.g., shor's algo)
asciilifeform: qc is not a wholly imaginary item, but a well-defined gadget proposed by r. feynman (naturally without schematics..)
asciilifeform: kinda curious which hardness puzzle they'll bless for 'q-resistant'
asciilifeform: hence my observation.
asciilifeform: aha
asciilifeform: hard to say, reads like the output of five separate monkeys who did not have any kind of complete picture each, other than a checklist of 'agenda items' to address
asciilifeform: s they have a long history of security evaluation and time tested implementation that newer proposals do not yet have.'
asciilifeform: 'It is important to note that we aren’t asking vendors to stop implementing the Suite B algorithms and we aren’t asking our national security customers to stop using these algorithms. Rather, we want to give more flexibility to vendors and our customers in the present as we prepare for a quantum safe future. Where elliptic curve protocols are to be used, we prefer Suite B standards be used to the fullest extent possible a
asciilifeform: what, thought mr mold & co invented it ?
asciilifeform: has been for 20yrs
asciilifeform: (can't recall this shit being in there earlier this year)
asciilifeform: new verbiage
asciilifeform: ^ l0l!
asciilifeform: te B algorithms, we recommend not making a significant expenditure to do so at this point but instead to prepare for the upcoming quantum resistant algorithm transition.'
asciilifeform: tandards bodies to ensure there is a clear plan for getting a new suite of algorithms that are developed in an open and transparent manner that will form the foundation of our next Suite of cryptographic algorithms. Until this new suite is developed and products are available implementing the quantum resistant suite, we will rely on current algorithms. For those partners and vendors that have not yet made the transition to Sui
asciilifeform: 'IAD recognizes that there will be a move, in the not distant future, to a quantum resistant algorithm suite. Based on experience in deploying Suite B, we have determined to start planning and communicating early about the upcoming transition to quantum resistant algorithms. Our ultimate goal is to provide cost effective security against a potential quantum computer. We are working with partners across the USG, vendors, and s
asciilifeform: was floored.
asciilifeform: the ozone.