asciilifeform: mnu's not unix!11 or wait that was a different fungus
asciilifeform: mircea_popescu: 2nd half of pdfturd is pretty great, internal memos etc , re full-bore gleichschaltung in full swing in all of the major sv saltmines
asciilifeform: ben_vulpes: the obvious n00b design mistake is the use of classical fixed-wings. if instead that petrol motor turned a dynamo, and powered (inefficient as may be) electrical multi-copter , a la toy store -- could do such things as following tree-lines etc.
asciilifeform: on own power, camel fuckers have serious problems making, i suspect, ~paper~ airplane.
asciilifeform: address all complaints to usg dept of state , who sends the model airplane kits to the orcs.
asciilifeform: didn't think it would make a palpable diff ( and it is not why i have it ) but still lulzy
asciilifeform just hung up a 4 square metre corkboard, interesting how room seems now quieter
asciilifeform thought this was clear from context, apparently this is a sin
asciilifeform: and hah, i think i finally see what mircea_popescu's objection was. no, thing dun have to physically store every byte of 'evil' output. elementarily a sabotaged fg will behave as prng.
asciilifeform: ( exercise for advanced reader : write a substitute evil_fg.v that fools a user who limits himself to the above test. )
asciilifeform: but at this point almost certainly repeating ancient thread.
asciilifeform: incidentally the 'pull out rng 'a', then 'b', then 'both', then...' test is a low-tech preventer of 'enemy intercepts parcel and reflashes the cpld to shit marsaglia prng'.
asciilifeform: but if you to compute the particular output expected for S1, S2 in advance, you gotta specify the clock freq, and run fg.v in e.g. 'verilator' . and it takes a while. )
asciilifeform: ( folx who ~did~ read it , know that it is possible to determine that a particular fg evaluates the same function on the input, for a particular string pair S1, S2 of bits, fed simultaneously into I1a, I2a, I1b, I2b, of FG a and b respectively; by syncing the oscillators , by connecting the 4th pins of a and b together.
asciilifeform: sometimes i wonder if mircea_popescu ever actually read the instruction.
asciilifeform: right. and if that's what you get out of the hose, you know that you've been slipped a fg that sha512('hurr'+sha512('hurr'....
asciilifeform: that ain't the output of the fg.v state machine tho.
asciilifeform: ok i'll bite, where does it store the correct-output corresponding to, e.g., tomorrow's #t log
asciilifeform: it's what that 4th pin on fg, is for.
asciilifeform: there is nuffin unreasonable about it, i just dun have the arse-mouth hoses set up atm.
asciilifeform: mircea_popescu: you would have to feed'em in pairwise ( or bit-interleaved ), as the thing has two 'mouths'. but otherwise yes, you feed'em in at particular clock, and oughta expect particular output.
asciilifeform: the standard yoke test is done against a known-good unit, rather than like this. ( why, is described in the log from late 2016 )
asciilifeform doesn't currently have the rig for this set up on desk
asciilifeform: you gotta feed it in at the requisite clock.
asciilifeform: i invite mircea_popescu to do it with 2 of his fg
asciilifeform: mircea_popescu: the yoke test consists of precisely this experiment
asciilifeform: i know exactly what's expected to come out for a given input
asciilifeform: http://btcbase.org/log/2018-01-12#1769493 << very basic specificity-of-diddling lemma. i.e. if i put today's trilema through it, it isn't as if it knows in advance that it ain't an analogue-rng-board plugged in, and what to shit out in response to a trilema that ain't yet been written☝︎
asciilifeform: dunno that this one'd make it to the top of the raging idiocies list; blood feud is lowest common denominator for revenge-plot
