log☇︎
77800+ entries in 0.037s
asciilifeform: and what else.
asciilifeform: dun forget, generals also
asciilifeform: aha!!
asciilifeform: or maybe i read it in ro, i faghet
asciilifeform: the one where 'come to moma's cunt ir we'll give yer wife anabortion every day'
asciilifeform: iirc you did translate
asciilifeform: and as always reader is presumed to count
asciilifeform: aha, for whom else
asciilifeform: snoaromatic
asciilifeform: 'nail that sticks up is hammered down' or how it went.
asciilifeform: http://www.returnofkings.com/wp-content/uploads/2017/07/influence-vs-enemy1.jpg << summary
asciilifeform: ( the 'influence' thing )
asciilifeform: BingoBoingo: that was a riotously terrifyingly stupid piece...
asciilifeform: lol
asciilifeform: r0nin-: ok
asciilifeform: r0nin-: dun go away, i'ma make a mirror just for ya
asciilifeform: betcha you played wolfenstein without the swasticas , with green blood, too..
asciilifeform: r0nin-: out of curiosity, where ? china ?
asciilifeform: evidently!
asciilifeform: aite.
asciilifeform: r0nin-: consider making a key?
asciilifeform: r0nin-: would you like to become.. a somebody?
asciilifeform: who might you be, r0nin- ?
asciilifeform: of course, arguably if you can actually DO this, you will probably lose interest in the mphf method per se
asciilifeform: ( http://btcbase.org/log/2017-07-04#1679049 was the other . ) ☝︎
asciilifeform: aha.
asciilifeform: ( as optimization )
asciilifeform: iirc i mentioned this to phf here.
asciilifeform: but instead flipping a single bit that gets xored with the result every time you read from the would-have-been-flipped reg. ☟︎
asciilifeform: by not actually doing the flip-whole-thing bit
asciilifeform: theoretically you can make it not.
asciilifeform: lolyes
asciilifeform: it sure does.
asciilifeform: and thereby any ~particular~ invocation, can be called bounded.
asciilifeform: was more of a philosophical observation : that mphf is not turing-complete ( in the same way 'p' is not. deliberately )
asciilifeform: and not 8999, and not 9001.
asciilifeform: and 9000 steps later, answer.
asciilifeform: why naturally you gave me a 9000 steps, and that's a, e.g., (TMSR!8192*3,50*9000)......
asciilifeform: (i.e. if you, yourself, already computed H(x), then you know how many turns of the crank it took. and can pass that number along.)
asciilifeform: i dun see how not.
asciilifeform: if it always terminates, then yes
asciilifeform: http://btcbase.org/log/2017-07-06#1679487 << thread, iirc ☝︎
asciilifeform: didn't i derive a bounding function for it...
asciilifeform: oh hm waitasec
asciilifeform: hm.
asciilifeform: aha!
asciilifeform: correct.
asciilifeform: you know ~that one~'s time and space size.
asciilifeform: yes but after you've calculated one particular hash, it won't vary...
asciilifeform: bang, magic, fixed-time-and-space.
asciilifeform: ~after~ a mphf (or similar) hash is taken, the time and space required are known.
asciilifeform: this means that anything that can happen inside one, happens in fixed time and space
asciilifeform: P proggy specifies its time and space requirement , first thing
asciilifeform: consider :
asciilifeform: lol just when i thought up of a hypothetical way to save it!111
asciilifeform: O(1)
asciilifeform: it's just a buncha xors
asciilifeform: why not ?
asciilifeform: am i missing something?
asciilifeform: but i dun see how they can live together
asciilifeform: well either it, or the constant-spacetime. and i'm quite sold on keeping the latter.
asciilifeform: asciilifeform's ~whole argument is 'leave as much rsa a matter for pubkey maker as physically possible'
asciilifeform: sure
asciilifeform: but sure.
asciilifeform: mircea_popescu: was thinking of the aerial gun in ww1, before they figured out that the stuff on the nonbusiness end dun have to be same bullet, only same mass
asciilifeform: yes i can think of a contrieved situation that calls for one. but no i don't want it in the rack next to the ordinary ones.
asciilifeform: non-1-to-1 pubkey is as useful as pistol that fires from both ends.
asciilifeform: to nail down the unambiguous and concrete.
asciilifeform: whole point of cryptosig is not-this.
asciilifeform: for others, no.
asciilifeform: shitting where one stands is also 'how life goes'. for some.
asciilifeform: it's like asking for a 17 that can also be referred to as 3.
asciilifeform: and there is no escape.
asciilifeform: this is fundamentally bad idea imho.
asciilifeform: http://btcbase.org/log/2016-12-27#1590895 , and http://btcbase.org/log/2017-04-09#1640824 discussions also. ☝︎☝︎
asciilifeform: http://btcbase.org/log/2017-06-01#1664352 << see also thread ☝︎
asciilifeform: how about an unshat-in vase.
asciilifeform: i dun see this picture, where we GOTTA take a shit into this here fine vase, 'or empire will'
asciilifeform: if some d00d wants to go around saying 'my pubkey can also be referred to by the letter z' that's his life to lose.
asciilifeform: but in not-standardizing.
asciilifeform: see asciilifeform's earlier barf: not so interested in forbidding anything
asciilifeform: no hash --- no collision, floating around somewhere in phase space waiting to be found.
asciilifeform: no moar fingerprints. your key is your key.
asciilifeform: fingerprints are fundamentally retarded
asciilifeform: likewise we had the fingerprint thread ☟︎
asciilifeform: http://trilema.com/2017/tmsr-rsa-spec-extremely-early-draft/#comment-122644 << 1st nitpick!1111
asciilifeform: oh hey
asciilifeform: ( while also operable on by machine, to demonstrate that the arithmetic in fact comes out as stated )
asciilifeform: in that spirit, other thing asciilifeform aims for with 'p', is to zap the idiocy where pubkey was strictly an item for ~machine~ to read, and make it something primarily for ~man~ to read.
asciilifeform: the duty of the rsatron author is ~to get the fuck out of the way~
asciilifeform: it is a matter strictly between the fella generating the key, and his wot, not for the author of rsatron.
asciilifeform: if i specify a pubkey for myself with 65536-bit public mod, then other people can simply decide that i'm an arse and that verifying my sigs isn't actually +ev for them
asciilifeform: so he can never be surprised by 'd00d's modulus is Too Big!111omfg'
asciilifeform: this means that the reader (READER, long before executing) knows precisely how much time and space the proggy requires.
asciilifeform: p proggy opens up with the breathoflife preamble, e.g., (TMSR!8192*3,50*500) << 8192bit bus, 3 words of stack, 50 bytes of program following the closing ), 500 steps of execution max.
asciilifeform: and this yes means that asciilifeform holds caps on modulus width to be asinine
asciilifeform: and this also means as few 'magic numbers' as it is physically possible to get away with. ☟︎
asciilifeform: asciilifeform's intent with 'p' is to push in the direction of maximum barking anarchy re pubkeys. as it is we have too many 'standards' as it is, ~all of them ill-conceived and smelling of sulfur.
asciilifeform: which
asciilifeform: no moar 'we heathens have faster rsa because mother dropped us as babies and our rsatron does different work on different hamming weights'