ben_vulpes: mircea_popescu: venmo is a touchscreen software abomination that claims to suck money out of one us account and put it into another
mircea_popescu: phf shorts because you probably tore proper pants by climbing into tree.
mircea_popescu: asciilifeform abandoned in 2011 ?
mircea_popescu: http://btcbase.org/log/2018-01-17#1771626 << shit i used to make these! 1992 represent!
a111: Logged on 2018-01-17 04:31 phf: oh, hah, i remember this "bytebeat" stuff, before it had a fancy name
a111: Logged on 2017-12-13 18:44 asciilifeform: and was played using clever method , where normally '1-bit' pc speaker membrane was allowed to travel 'partial' way , squeezing extra 'bitness'
mircea_popescu: http://yehar.com/blog/?p=893 << how to save 50 euro for the cost of five plus liberal application of your time (which has no value).
Techman: mircea_popescu: what isy our take on bitcoin dropping below 10K (at least on binance)
apeloyee: http://btcbase.org/log/2018-01-16#1771008 << I doubt you actually understood why (If you had, you would be a lot more worried, per http://btcbase.org/log/2018-01-16#1771010 ). here's a simpler version of the puzzle: http://p.bvulpes.com/pastes/UmpSH/?raw=true . has exactly the same bug.
a111: Logged on 2018-01-16 15:15 asciilifeform: and yes his example snippet ~will~ barf. and no i won't spoil the puzzle by saying where and how. and no it is not hard to make 9000 similar examples.
a111: Logged on 2018-01-16 15:15 asciilifeform: if anyone finds so much as the smell of one -- i would like to hear about it, asap.
apeloyee: http://btcbase.org/log/2018-01-16#1771004 << it's not me that does it at the expense of obvious correctness, but _you_. instead of having the compiler enforce no access to Stack(0), one is forced to rely solely on manual checking. But enough about that trivial matter; I'll just make the change locally.
a111: Logged on 2018-01-16 15:13 asciilifeform: and willing to do so at the expense of obvious correctness ?
esthlos: http://btcbase.org/log/2018-01-16#1771055 << My thought was to scrap the current client in favor of a customized one, with eucrypt protocol as the backbone. Is this 1. not what you want, or 2. a bad idea?
a111: Logged on 2018-01-16 15:57 mircea_popescu: http://btcbase.org/log/2018-01-16#1770890 << to be clear, the idea here is that you pick up the extant eulora client, gut it of the current eulora functionality, put eucrypt in there and proceed to implement your idea. this way you have a proved-to-cross-compile platform to start from.
esthlos: Rereading, seems clear that you want eulora's graphics engine.
esthlos: Alternative is stupidly simple text-driven client; downloads multimedia using eucrypt
shinohai: Text-driven client is the holy grail for some of us Eulora people.
esthlos: shinohai: I've targeted this as my first real contribution to la serenissima
shinohai: You have my full support, and will be glad to help read/test any code you produce.
shinohai: I started some work on this over a year ago, simply too much work for me because of irl obligations unfortunately.
diana_coman: esthlos, "current eulora functionality" has nothing to do with graphics really; and client is totally up to players
diana_coman: you can play it with whatever client you want, that's the point
jhvh1: shinohai: The operation succeeded.
asciilifeform: http://btcbase.org/log/2018-01-17#1771637 << your item clobbers the modulus as it runs. what i dunget, is why this would justify making the range of SP wider than Stack itself, as seen in your paste earlier.
a111: Logged on 2018-01-17 11:22 apeloyee: http://btcbase.org/log/2018-01-16#1771008 << I doubt you actually understood why (If you had, you would be a lot more worried, per http://btcbase.org/log/2018-01-16#1771010 ). here's a simpler version of the puzzle: http://p.bvulpes.com/pastes/UmpSH/?raw=true . has exactly the same bug.
asciilifeform: http://btcbase.org/log/2018-01-17#1771640 << MustNotZero has 0 to do with Stack(0), it is there to keep the tape from creating a div0
a111: Logged on 2018-01-17 11:28 apeloyee: http://btcbase.org/log/2018-01-16#1771004 << it's not me that does it at the expense of obvious correctness, but _you_. instead of having the compiler enforce no access to Stack(0), one is forced to rely solely on manual checking. But enough about that trivial matter; I'll just make the change locally.
asciilifeform: and no, not 'enough', i'd like to find out wtf apeloyee was thinking
asciilifeform: specifically, why :
asciilifeform: subtype Stack_Positions is Natural range 0 .. Height;
asciilifeform: type Stacks is array(Stack_Positions range <>) of FZ(1 .. Wordness);
asciilifeform: - Stack : Stacks(Stack_Positions'Range);
asciilifeform: + Stack : Stacks(1..Height);
shinohai: Logged: 09:17 +Hasimir and yes, libgcrypt is part of the larger project, Werner and Niibe are at the core of GNU security.
asciilifeform: the proper way to enforce 'no access to Stack(0)' would be to constrain Stack_Positions to 1 .. Height. but this leaves no way to represent an empty stack.
shinohai: !~ticker --market all
jhvh1: shinohai: Bitstamp BTCUSD last: 9568.75, vol: 38790.17876819 | Bitfinex BTCUSD last: 9459.4, vol: 131533.8373469 | Kraken BTCUSD last: 9569.0, vol: 10706.6833868 | Volume-weighted last average: 9489.31292948
esthlos: diana_coman I didn't mean to imply it would be "official" (tm) client
esthlos: but having one in existence would help fellows in shinohai's position
diana_coman: esthlos, certainly, not an issue; I think you are overthinking/overreading into this
shinohai: Well as diana_coman said, Eulora encourages one to customize to one's liking.
shinohai: You can play with pen and paper, I'm sure, if you find a method for so doing.
diana_coman: and fwiw see history of foxybot: it started precisely like that, as a player-made-for-own-use thing and it ended up bundled into "official" client
diana_coman: not by accident either; it's s.mg policy
shinohai snail-mails diana_coman all my claim updates, looks around forlornly as they all vanish into lbn ....
diana_coman: now hmm, where was that bit written on trilema
diana_coman: esthlos, here it is: http://trilema.com/2015/ok-so-what-is-eulora-disrupting/
apeloyee: MustNotZero has 0 to do with Stack(0) << I know.
shinohai: Round 1 .... FIGHT, FIGHT, FIGHT!
apeloyee: Hear, hear! If asciilifeform would agree to take discussion of why 1+1=2 elsewhere, I'll do.
asciilifeform: apeloyee: let's hear the answer to the riddle ?
asciilifeform: i'ma listen
asciilifeform: both parts
apeloyee: the change to size Stack in the first paste was irrelevant
apeloyee: *size of Stack
asciilifeform: that part i get, it doesn't have anything to do with the clobbering of the modulus
apeloyee: why should correctness depend on order of the arguments?
apeloyee: (on FFACalc stack)
asciilifeform: because we're overwriting an input ?
asciilifeform: could just as easily not, with temp buffer. but why.
asciilifeform: it is not my place to make every possible mutilation of the program, safe. ( and is quite impossible )
asciilifeform: prolly FZ_Mod_Exp oughta accumulate Product in a temp, and shit it out in 1shot in the end, like FZ_Mod_Mul.
asciilifeform: though it is a waste of space and time.
asciilifeform: i never proclaimed, fwiw, that all ffa routines must be able to cleanly walk over own inputs.
apeloyee: what functions can tolerate aliasing of arguments is talked of precisely nowhere. and it's easy to forget about that when changing them later. and aliasing is used extensively.
apeloyee: so can't say "don't do that"
asciilifeform: used extensively ? where, other than the stack ops ?
apeloyee: is invoked many times with output = one of inputs
esthlos: diana_voman very likely am over thinking things
esthlos: lol diana_coman
asciilifeform: has apeloyee found a specific instance where it can be made to eggog ? or is this a hypothetical 'once less clueful people start changing things' observation ?
esthlos: I will proceed one step at a time
apeloyee: the latter.
asciilifeform: because there isn't actually a limit as to what less-clueful people can break, regardless of what i do
asciilifeform: but i can't help but agree with apeloyee re the Product in FZ_Mod_Exp , it gotta be buffered.
diana_coman: esthlos, lol! auto-completion helps
asciilifeform: the cost is small in comparison with the mod-exping per se
apeloyee: this can be used to justify pointer arithmetic and what-not. Just don't do unsafe things!!
apeloyee: FZ_Mod_Mul also
asciilifeform: the ch7 one ? yea
apeloyee: (as implemented in chapter 7, but not chapter 6)
asciilifeform: i'ma buffer'em.
asciilifeform: really all routines oughta behave consistently in re input-overwrite.
shinohai: Diana Voman sounds very Soviet to me for some reason.
asciilifeform: this is a bit of a downer, i confess that i hoped apeloyee had found a more subtle, lethal boojum.
apeloyee: and add a new exercise: re-read all previous chapters and write what aliasing of arguments is safe
asciilifeform: apeloyee still wins 'most attentive eagle eye' award.
asciilifeform: the 1 caveat re buffers, is that there is a practical limit as to what can be made anticlobbering: if i were to do it to items that occur in inner loops of O(n^3)istic items, e.g. mux, proggy will end up 'geological' 4ever.
apeloyee: I think everything up to ch.5 is safe as long as arguments are either equal or don't overlap
apeloyee: *memory locations of the arguments
asciilifeform: afaik it isn't actually possible to write overlap-safe routines without implicit (or otherwise) branches
asciilifeform: in the general case.
apeloyee: does gnat provide a facility to check aliasing at runtime?
asciilifeform: partially ( for array copies ) . but it gets nuked by No_Implicit_Conditionals.
asciilifeform: ffa itself is a sort of tightrope walk, an attempt to 'и рыбку съесть и нахуй сесть' . it isn't actually possible to make all of the routines able to take every conceivable kind of compile-time abuse ( which i'd argue overlap of arguments, is ) without conditional jumps.
apeloyee: conditional jumps are OK if one of the destinations just aborts the program
apeloyee: as with MustNotZero
asciilifeform: right, e.g. the range checks
asciilifeform: ( they don't appear in the code, but they exist )
apeloyee: aliasing checks are like range checks in this regard
asciilifeform: No_Implicit_Conditionals does not affect such jumps however
asciilifeform: ( observe , they are still present in the disasm )
apeloyee: then why "it gets nuked by No_Implicit_Conditionals."? wreckers (tm)?
asciilifeform: it isn't a wrecking
asciilifeform: No_Implicit_Conditionals is working as described on the box : https://docs.adacore.com/gnathie_ug-docs/html/gnathie_ug/gnathie_ug/using_gnat_pro_features_relevant_to_high_integrity.html#controlling-implicit-conditionals-and-loops
asciilifeform: and afaik gnat does not know how to prevent aliasing in the general case, but only in a few specific situations ( array copies )
apeloyee: well, ideally it would have a "No_Out_Arguments_Aliasing" restriction which would insert runtime checks
asciilifeform: but afaik no such item exists , even in '2012'
apeloyee: gnat implements many nonstandard restrictions
asciilifeform: possibly one can make a SPARKistic proof of non-aliasing , for proggy taken as a whole. i'ma look into it.
asciilifeform: thing is, a sparkism is not a substitute for a 'fits-in-head'-correct routine.
asciilifeform: proggy ought to be written in such a way that the reader can ~see~ that it is correct.
asciilifeform: this is the #1 type of stylistic fix that i look for -- 'can this be made more obviously-correct-when-used-as-prescribed' and 'can use-as-prescribed be made more obvious'
apeloyee: yes. hence me bringing this item here
asciilifeform: aha. ty apeloyee , for taking the sweat to do this.
asciilifeform: i'm still curious re the SP tho
asciilifeform: can you think of a way to have the range of SP and of Stack be the same, but to still represent concept of 'empty' ?
BingoBoingo: !~ticker --market all
jhvh1: BingoBoingo: Bitstamp BTCUSD last: 9962.0, vol: 43036.01398257 | Bitfinex BTCUSD last: 10082.0, vol: 142442.83558633 | Kraken BTCUSD last: 10048.3, vol: 11690.3715496 | Volume-weighted last average: 10053.8095595
asciilifeform: oh hey waterfall working again
a111: Logged on 2017-01-16 18:11 jhvh1: BingoBoingo: Bitstamp BTCUSD last: 828.5, vol: 5371.02382600 | BTC-E BTCUSD last: 819.819, vol: 4067.02976 | Bitfinex BTCUSD last: 827.09, vol: 7289.43424066 | BTCChina BTCUSD last: 820.81503, vol: 506972.47910000 | Kraken BTCUSD last: 834.0, vol: 1190.23580128 | Volume-weighted last average: 821.002992125
BingoBoingo: 10+x crashing over last year
asciilifeform: BingoBoingo: hey they only nao plugged it back in
BingoBoingo: Nah, this appears to be an Azn attempt at replicating white person's waterfall
shinohai: Gotta sell all my Bitcorn before the Missus finds out I spent all our monies on the Bitconnect ponzi.
apeloyee: can you think of a way to have the range of SP and of Stack be the same << this is plainly absurd. a N-sized stack has (modulo contents) N+1 possible states: "0 elements", "1 element", ..., "N elements". i.e.the ranges MUST differ, by exactly one.
BingoBoingo: In other shithole factories: meltdown/specte patches are making a bunch of industrial systems wobble! Chinesium's about to get a low more Pinoy
asciilifeform: apeloyee: i dunget why absurd ? my other arrays behave this way.
asciilifeform: i.e. in all cases where the array has a custom indexing type as the index, the array exists over the entire range of said type.
asciilifeform: concretely, e.g., Dividend_Index in http://btcbase.org/patches/ffa_ch7_turbo_egyptians#L31
asciilifeform: apeloyee: a long-term goal is to have the whole proggy bulletproof even after building under '-gnatp' ('disable all range checks'). relying on the range check of Stack , vs SP's range, does not go well with this
apeloyee: Logically, SP isn't a reference. It's a cursor, showing the boundary between the valid and invalid elements. If a line in a text editor has N sybols, then a cursor has N+1 valid positions. (Consider that an empty line sill has 1 valid cursor position).
asciilifeform: ideally there would be some way to trap any reference to the zero cell, or , failing that, to prove that the zero cell cannot end up referenced.
asciilifeform: apeloyee: well yes, i get it. but i DON'T LIKE it.
asciilifeform: i'd like to resolve the apparent contradiction between 'all possible SP positions are valid dereferences' and 'stack can be empty'.
apeloyee: an extra element won't save the father of russian democracy (c), if FFACalc stack manipulation code is wrong; e.g. if a 'Want(X)' statement is omiitted
asciilifeform: right. but why would it be omitted.
asciilifeform: one way i considered doing this, is to do away with all such things as 'SP - 1', 'SP - 2', etc. and instead to have e.g. Get_Stack_First, Get_Stack_Second, etc., each of which individually would ensure that the desired element exists. but these would have to return 'access type' (pointers) which thus far i've avoided using .
apeloyee: if FFACalc code is correct, then it's also safe to omit that zero-indexed element from Stack
asciilifeform: this is true. but 1) ugly 2) possibly will get in the way of sparkism, later; it relies on type ranges for good chunk of the proofolade
asciilifeform: hmm, what if one were to model SP as in apeloyee's analogy, the text editor cursor. i.e. the pos of the ~next~ valid stack cell, rather than 'current'.
asciilifeform: then to refer to current, would be 'SP - 1' rather than 'SP'
apeloyee: no need
apeloyee: cursors are pointing _between_ elements
asciilifeform: well it'd turn a pop from empty stack into a range-dipping eggog instantly
asciilifeform: and abolish need to want()
asciilifeform: ( at the very least, if range checks are enabled for ffacalc )
asciilifeform: there's an explicit range test construct, btw
apeloyee: the proper range for a cursor into an array (1..N) is (0.5 .. N+0.5); this is usually shifted to become (1 .. N+1) as in text editors, but no reason not to shift in the other direction, as you did, to (0..N)
apeloyee: (other than convention)
apeloyee: SP _is_ a cursor, I'm merely suggesting to treat it as such
apeloyee: "1) ugly" << can't see that.; "2) ... it relies on type ranges for good chunk of the proofolade"<< if you really want, can explicitly declare a subtype of Stack_Positions, omitting 0 from it
apeloyee: that _would_ be ugly indeed
apeloyee: well it'd turn a pop from empty stack into a range-dipping eggog instantly << the reason I even suggested that 3 weeks ago
a111: Logged on 2017-12-08 13:39 asciilifeform: meanwhile, on the hannoboeck planet, https://neopg.io << usg tool marcus brinkmann proclaims 'clean rewrite of gpg' , with fanfare, spamola ( e.g. http://www.openwall.com/lists/oss-security/2017/12/08/1 ) , 'modernisms', the full shebang.
asciilifeform: apeloyee: afaik it isn't possible to make types 'with hole'
apeloyee: 0 is at the boundary
asciilifeform: so what would empty stack look like , in this variant ?
apeloyee: as in my patch
asciilifeform: this is not equiv to cursor behaviour in text editors, though. there, cursor always is pointing to a valid fillable cell
a111: Logged on 2018-01-17 17:03 apeloyee: the proper range for a cursor into an array (1..N) is (0.5 .. N+0.5); this is usually shifted to become (1 .. N+1) as in text editors, but no reason not to shift in the other direction, as you did, to (0..N)
asciilifeform: currently seems to me that ~all~ of the possible variants, are similarly ugly
apeloyee: what's ugly about my proposal? only two lines changed
asciilifeform: the fact that an array is indexed by a type which has a range outside of the array's.
asciilifeform: at the risk of repeating myself.
asciilifeform: ideally there would be NONE of any such thing, in the entire program.
asciilifeform: i.e. if you see an array reference, you ~know~ that it is valid, because of the type of the index.
a111: Logged on 2018-01-17 16:43 asciilifeform: concretely, e.g., Dividend_Index in http://btcbase.org/patches/ffa_ch7_turbo_egyptians#L31
asciilifeform: mine is also ugly, it is conceivable that somebody, some day, in a broken variant and running with -gnatp, ~will~ write to the zero cell
asciilifeform: this however is preferable than writing to the return addr on the stack !
asciilifeform: *preferable to
asciilifeform: the fundamental riddle is whether this is an ~avoidable~ instance of http://btcbase.org/log/2016-01-21#1379603 -ism
a111: Logged on 2016-01-21 13:29 asciilifeform: 'if i make it what i think is the right size, it crashes!111'
apeloyee: ~will~ write to the zero cell << why not to minus-one cell then
asciilifeform: i was about to add :
asciilifeform: possibly there ought to be not 1 but... 4 null cells
asciilifeform: to carry this to logical conclusion
asciilifeform: ( i.e. equal to the arity of the highest-arity stack op )
asciilifeform: the other open q is where to draw the line re 'somebody, some day, with mutilated ffa' .
asciilifeform: because it gotta be drawn somewhere.
apeloyee: doesn't gnat have a facility to control the layout of memory?
asciilifeform: what do you have in mind, apeloyee ?
apeloyee: put a dummy array of 4 (or whatever) elements just before the Stack
asciilifeform: there is not, afaik, a way to force stack frames to be explicitly padded
asciilifeform: and at any rate the right place for such a thing is in the code, rather than in the guts of the linker
asciilifeform: pc arch also does not, unfortunately, give a way for userland to trap on reads/writes to specific piece of memory
asciilifeform: this is a fundamental headache
apeloyee: Don't Turn Off Bounds Checks.
apeloyee: and there's no problem.
asciilifeform: easy to say on 3GHz+ pc
asciilifeform: how about when it goes in a 25mhz micro ?
asciilifeform: i don't see any reason why the thing should ~rely~ on adatronicn bounds checks for correctness.
apeloyee: it... doesn't?
asciilifeform: well right now it doesn't
apeloyee: Want(); etc
asciilifeform: ideally could somehow get rid of want() tho, AND not rely on implicit bounds checks
asciilifeform: AND be correct-to-naked-eye
apeloyee: "five-angled heptagon"
asciilifeform: or maybe not. i say it is an open problem.
asciilifeform: ftr several different items in ffa seemed to me to be 'five-angled heptagons' (starting with how to compute the asm-less addition carries) until i solved'em
asciilifeform: one way to model this process is that there is an 'ugliness budget', just like there is a cpu cycle budget, that can be 'spent' in certain ways
asciilifeform: ideally so as to maximally compartmentalize and document the ugly
asciilifeform: or for another example, take the ugliness and 'pointericity' of the traditional 'pivoting' form of karatsuba. which i killed by forcing all FZ bitnesses to be powers of 2.
asciilifeform: incidentally there were pivot-position bugs in commonly-used karatsubas as late as the early 2000s.
asciilifeform: ( prolly still are today, somewhere in ssl liquishit )
asciilifeform: apeloyee: here's another idea from my notes , that would do the job : to dispense with the array representation for the stack, in favour of linked list. ada permits the definition of a 'not null' pointer type (whose non-nullity is checked on every reference) .
asciilifeform: however this introduces explicit pointerism. ( though, i will add, NOT pointer-arithmetism )
asciilifeform: want() would then vanish; both stack underflow and overflow checks would be handled by the nullity check ( first cell has a null in its 'prev' slot; last cell in stack -- in its 'next' . )
asciilifeform: whether this is cleaner than the existing item, i will leave up to the readers, incl. apeloyee .
asciilifeform: currently it actually seems to me , to be cleaner -- in that its correctness proof is simpler, does not use arithmetic at all
asciilifeform: you can trivially show that any attempt to walk under or over the stack, would have to involve a null-dereference.
asciilifeform: nao that i think about it, it doesn't even have to introduce 'access types' ( pointers in ada ) , can use ordinary integers
asciilifeform: so a stack cell would contain not only an FZ of the current bitness, but two boolean values, e.g. HasPrev and HasNext
asciilifeform: the first cell has a false HasPrev ; the last -- a false HasNext.
asciilifeform: ( i will omit the rest of the mechanism, i think it is pretty obvious )
apeloyee: it's a wonder -gnatp doesn't disable nullity checks
asciilifeform: doesn't seem to , in gnat '2016'
asciilifeform: but this is one of the reasons why there is no escape from disasm
asciilifeform: will have to see what gets removed, what -- not
asciilifeform: the variant with booleans doesn't rely on non-nullities tho.
asciilifeform: it's simply an arithmetic-free version of want().
asciilifeform: speaking of which, could even have a stackmachine with circular ring for a stack.
asciilifeform: ( i'd rather not. but there is nothing fundamentally unusable about it )
apeloyee: https://gcc.gnu.org/onlinedocs/gnat_ugn/Alphabetical-List-of-All-Switches.html#Alphabetical-List-of-All-Switches : "-gnateA" Check that the actual parameters of a subprogram call are not aliases of one another.
asciilifeform: oh hey neato
asciilifeform: apeloyee: do you know how it behaves under -gnatp ?
apeloyee: no idea. just found.
asciilifeform: ( other q is whether it understands overlaps, as well as exact-match aliases )
asciilifeform: !!up freetlas
deedbot: freetlas voiced for 30 minutes.
asciilifeform: who might you be , freetlas ?
freetlas: Wow, first time I see too many people in here :o
asciilifeform: freetlas: you did not answer the question
freetlas: asciilifeform: Just a person who likes to read trilema from time to time :)
apeloyee: from above: "Check that the actual parameters of a subprogram call are not aliases of one another. To qualify as aliasing, the actuals must denote objects of a composite type, their memory locations must be identical or overlapping, and at least one of the corresponding formal parameters must be of mode OUT or IN OUT. "
asciilifeform: apeloyee: neato. gotta wonder how this is implemented tho.
apeloyee: this is gpl gnat tho
asciilifeform: i can't picture how without a megatonne of conditionaljumps. but maybe just failure of my imagination.
apeloyee: of unknown version
apeloyee: nuffin wrong with conditional jumps, if one destination aborts.
asciilifeform: from leakage pov yes
asciilifeform: from pipeline-blowing pov -- expensive.
apeloyee: prediction would be perfect
asciilifeform: if gcc actually puts in the 'jump-likely' . currently i have nfi whether it does.
Covale`: http://btcbase.org/log/2018-01-17#1771610 - no, not mine, I don´t have one. Neither do I have that cup, but it´s a pretty decent Lenin nonetheless
a111: Logged on 2018-01-17 01:29 mircea_popescu: http://btcbase.org/log/2018-01-16#1771435 << hey, is that your blog then ?
BingoBoingo: Now that was a wasted voice
apeloyee: http://btcbase.org/log/2018-01-05#1765560 << this looks to be the only safe way. asciilifeform : don't you think that's insane?
a111: Logged on 2018-01-05 23:30 asciilifeform: trinque: if you really hate files, you are welcome to make the whole proggy 1 file
BingoBoingo: It gets 30 minutes with the audience, remarks on the size on the audience, and then silence
asciilifeform: apeloyee: waiwat
asciilifeform: i must've missed something
apeloyee: a vpatch's purpose is twofold. 1) to provide a way to construct some files based on some antedecent files, whose hashes are given. 2) to take some responsibility about the entire tree. but the signature on a vpatch doesn't fix the state of the tree; it is defined implicitly by antedecent patches, which are liable to change at any time ("regrinding") and thereby change some files not...
apeloyee: ...referenced in a particular vpatch
apeloyee: hence the hash-manifest proposals
asciilifeform: apeloyee: the 'liable to change' thing was very much NOT part of my orig design for v.
apeloyee: really it's CVS over again
asciilifeform: imho it is an abuse.
asciilifeform: apeloyee: some of the 'cvsism' is deliberate -- cvs made collaborative writing harder by accident, we -- on purpose !11
apeloyee: files are NOT INDEPENDENT. despite CVS and v pretending they are. this is a problem. you could have required some form of cryptographic commitment to either the tree state or even the antedecent patches themselves, but didn't
asciilifeform: apeloyee: see the quite 'flammable' log from that thread. i put the burden of correct operation ~100% on the human operator.
asciilifeform: apeloyee: trinque and mircea_popescu would like to put more of it on the machine. i haven't with what to dissuade them, it is a philosophical q, not even technical.
asciilifeform: and yes it is entirely true that files-are-not-guaranteedly-independent.
apeloyee: do you advocate the brick "lisp machine", too?
asciilifeform: hey it's the only kind i have nao!11
asciilifeform: ( asciilifeform traded his lispm for two last-made lispm single-ic cpu... )
apeloyee: well, your point seems to be specifically that work which can be done by machine is shifted onto a human. this is insane.
asciilifeform: as i described in the linked thread, forcing the entire program under the antecedent hasher is not free
asciilifeform: it severely constrains the kind of things you can do without manual surgery
asciilifeform: so it is not correct to say 'you made the man do what the machine could do.' rather, lightened the work for operator for one kind of operation, and made heavier -- other kind.
BingoBoingo: And in other news, a police car exploded near the Brazilian border https://www.elobservador.com.uy/bomberos-explosion-auto-policial-fue-intencional-n1160744
asciilifeform: BingoBoingo: and on most days they do not ?
asciilifeform: fenómenos que "no tiene antecedentes" en el país << orly?
BingoBoingo: On most days they do not explode on this side of the border.
asciilifeform: ( it borders, e.g., columbia. nothing exploded there ?0 )
BingoBoingo: The closest thing so far was they time an Israeli embassy worker was busted with a bomb or fake bomb near the WTC
BingoBoingo: asciilifeform: Uruguay pointedly does not border Columbia. Other side of the Continent
asciilifeform: i was speaking of brazil
BingoBoingo: Anyways Artigas is about as far north as you can get in Uruguay.
apeloyee: that's a spurious objection. one need not to sign an antedecent state, one needs to sign a RESULTING state. to expand on http://btcbase.org/log/2018-01-17#1771900 , you're free to pick individual files from wherever, possibly several different trees, but there needs to be a tree hash in the _leaf_ patch. and it MUST match the resulting tree (under the principle that patch author takes the...
a111: Logged on 2018-01-17 19:31 apeloyee: a vpatch's purpose is twofold. 1) to provide a way to construct some files based on some antedecent files, whose hashes are given. 2) to take some responsibility about the entire tree. but the signature on a vpatch doesn't fix the state of the tree; it is defined implicitly by antedecent patches, which are liable to change at any time ("regrinding") and thereby change some files not...
apeloyee: ...responsibility for the resultant tree state).. otherwise it's unclear what one signs.
trinque: they're equivalent neh? signed antecedent state or signed resulting state + fact that the patch is signed
trinque: and in the case of signed antecedent state, don't have to press first to know if you could
apeloyee: well, a hash is not the same as the signature, but otherwise yes.
apeloyee: but there can be several of them
apeloyee: for merging
trinque: pretty obvious I'm saying signed hash, i.e. hash is in the signed vpatch
asciilifeform: trinque is right tho, they are equivalent
asciilifeform: and in both cases, the ability to explicitly mark subsystems as independent ( e.g. a readme.txt being independent from doesallthework.adb ) is lost.
asciilifeform: iirc mircea_popescu's argument was that it is wrong to say that they could ~ever~ be properly independent. and that if they could be shown to be independent, they ought to be separate v-trees.
asciilifeform: i don't have a good counter-argument to this.
asciilifeform: however it DOES mean even ~more~ work for folx using v, than ever before. and not less.
asciilifeform: potentially exponentially more.
asciilifeform: for multi-author projects, that is.
asciilifeform: for single-author, e.g. ffa, nothing really changes.
trinque: asciilifeform: to see if I can restate your opinion back to you, if I edit (as single author) both readme.txt and doesallthework.adb in separate vpatches, your view is I combine those into a single vpatch, if I want to build atop both in a new vpatch?
asciilifeform: trinque: under classical v, or trinqueian ?
asciilifeform: under classical, you can grab antecedents from any trees you want, by copying files, aha
asciilifeform: as i did in trb.
asciilifeform: so answ to trinque's q is yes
trinque: then we are closer than it appeared in the long thread. I proposed being able to name arbitrary required antecedents in a vpatch's header, and this appears equivalent in effect to copying the file in whole.
fromloper: asciilifeform: someone uploaded "I-Machine Architecture Specification" to Bitsavers three days ago, I thought you might find it interesting: http://www.bitsavers.org/pdf/symbolics/I_Machine/I-Machine%20Architecture%20Specification.pdf
fromloper: it's more complete than the previously published documents on the Ivory
asciilifeform: fromloper: pretty sure i've seen this before
fromloper: there were older versions of three chapters from this documents on Bitsavers, but not the whole thing
apeloyee: point is, the situation when you can replace one of the patches with figurative "format c:" and 'v' will be none the wiser as long as the file is not touched by later patches is insane
asciilifeform: fromloper: it is not a complete arch description, you cannot write a working emulator with it ( or even make the existing snap4 not-crash )
asciilifeform: fromloper: i'ma look. ty
fromloper: did you succeed in scanning the chip at Zeptobars?
asciilifeform: apeloyee: there is not a mechanical solution to preventing someone from 'putting in format c:' proverbially
asciilifeform: fromloper: that was phf's plan. afaik he has not, as of yet.
asciilifeform: fromloper: i shopped around in commercial labs; the best bid was in the neighbourhood of 25,000 usd.
apeloyee: when you sign a tarball, the signature is not transferrable to anything else
asciilifeform: fromloper: that's where it stopped. i do not have 25k usd to use on ivory die photo.
asciilifeform: apeloyee: observe , i do not actually disagree .
fromloper: I see, hopefully phf will have more luck with Zeptobars
asciilifeform: apeloyee: trinqueian / mircea_popescuine vtron is arguably The Right Thing. my observation is that it may be a 50kg sword.
asciilifeform: fromloper: i only have two 'ivory' chips, and ideally would like to leave one intact , for active test . iirc phf also has 2 to use.
asciilifeform: so i'ma save mine for proper commercial lab. but that means potentially forever. maybe whoever takes it off my corpse, can get it photo'd.
apeloyee: "may be a 50kg sword" << doesn't seem to be. can be retrofitted into an existing design. as i said above "there needs to be a tree hash in the _leaf_ patch. and it MUST match the resulting tree"
asciilifeform: retrofitted yes
asciilifeform: but i am speaking of ~use~.
fromloper: asciilifeform: if I remember, you wanted to hook this intact chip to some emulation of Ivory's life support
asciilifeform: fromloper: correct
asciilifeform: fromloper: currently however i do not even know where the power supply pins are, much less bus addressing, i/o, clock, etc
asciilifeform: or the necessary timings.
asciilifeform: ( or what it expects to find on the bus, or almost anything else )
asciilifeform: i do not have, nor ever had, a working 'ivory' of any description.
fromloper: VLM is not very informative for this purpose, unfortunately
asciilifeform: fromloper: correct. almost totally useless.
apeloyee: I proposed being able to name arbitrary required antecedents << also probably needs a mechanism to declare "there are no other files in the tree"
asciilifeform: apeloyee: look at the trb tree, and picture what the mass of the patches would have been, if this requirement had been in effect when i made it.
asciilifeform: ( and yes mircea_popescu's answer was 'shuddup and suck it' . which is very easily said when you ain't the one sucking it )
asciilifeform: fromloper: i'll confirm, this is a larger and moar detailed document than old one.
apeloyee: a hash of the entire tree doesn't take much
fromloper: at the very least, the description of the instruction set is much more complete, all the opcodes are listed and no blanks at all
fromloper: there is a whole section on the virtual memory
fromloper: though it's still an early version of the architecture, revision 0 if I understand correctly
fromloper: the last one is rev 5
fromloper: which was designed for VLM exclusively
fromloper: asciilifeform: I have noticed that some of the former Symbolics employees are fairly active on Twitter, like https://twitter.com/swmckay (one of the developers of VLM) and https://twitter.com/KalmanReti , do you think it is possible to pry any information out of them?
apeloyee: !#s whisperers
asciilifeform: fromloper: possibly. my track record for prying information out of bolixologists is ~0 so far, however.
asciilifeform: somehow we cannot find common language, i have nfi.
asciilifeform: fromloper: looking at the linked doc, it is indeed very useful, now we have maybe 80% of the necessary info, instead of ~50%.
fromloper: asciilifeform: very good, I'm glad I brought it to your attention
asciilifeform: http://btcbase.org/log/2018-01-17#1771995 << in these pages however all i see is claptrap re 'racism of trump', 0 about lispm
a111: Logged on 2018-01-17 20:24 fromloper: asciilifeform: I have noticed that some of the former Symbolics employees are fairly active on Twitter, like https://twitter.com/swmckay (one of the developers of VLM) and https://twitter.com/KalmanReti , do you think it is possible to pry any information out of them?
trinque: pretty common to end up LARPing in retirement, even if one lived as a man, unfortunately
asciilifeform: the unfortunate bit is that reti et al seem intent to take their seekritz to their graves, because they are 'law-abiding' and are still honouring their nda to the dead hand of the dead man
asciilifeform: trinque: aha
fromloper: yeah, somehow a lot of potentially interesting people on social media end up mostly posting this kind of crap
asciilifeform: think, somebody, somewhere, has the source code to ns. and the ns netlist , with comments, to the ivory.
asciilifeform: he ain't sharing.
asciilifeform: somebody shares ? i'll read, even if he also goes on re 'racism'
asciilifeform: but somehow never happens.
asciilifeform: somebody , maybe same old man, has a bookcase full of typewritten design apocrypha, memoes, etc. from ivory group. he ain't sharing either.
asciilifeform: out of fear of usg ? or from vanity ( he thinks it can be sold for millions ? to whom ? ) he is burning his life's work. i have nfi why.
fromloper: this document refers to Dave Moon's files several times; I've tried to find any public presence of Moon on the net, maybe a mail address - found nothing
asciilifeform: funnily enuff a Dave Moon ran for election to some city dogcatcher post , not far from where i live. but on examination seems to be different d00d.
asciilifeform: the original may well be dead
asciilifeform: weinreb died a few yrs ago
fromloper: Moon had an interview with Azul Systems' people in 2008
fromloper: that's the last of him I found
asciilifeform: i recall this
asciilifeform: and i haven't seen him anywhere since, either
asciilifeform: http://users.rcn.com/david-moon/MMD/HTML/index.html << apparently was at least alive in 2016
asciilifeform: 'Comments and criticisms to dave underscore moon atsign alum dot mit dot edu. ' << anybody tried ?
asciilifeform: and now that we're on subj , where is, e.g., r. d. greenblatt ?
asciilifeform: tom knight ?
fromloper: so there is at least one possible address, gotta try it
fromloper: Tom Knight is working with biologists
asciilifeform: that was last i knew aha
asciilifeform: 0 to do with lispm, for ~3 decades
asciilifeform: but apparently alive.
fromloper: Richard Greenblatt helped with this in 2006 https://projects.csail.mit.edu/films/aifilms/AIFilms.html
asciilifeform: and yes the ones still alive, all work ~somewhere~, symbolics did not make anybody aside from the yacht brahmins rich
asciilifeform: ( in usa for some reason it is traditional for ceo to be paid mega-bonus even when the company tanks )
fromloper: afaik Symbolics was changing CEOs like gloves
asciilifeform: it was
asciilifeform: whole buncha upper crust parasites gotta be buttered, apparently.
asciilifeform: to be fair the company was not really a honest commercial co, moar like one of those unofficial usg research institutes, they proliferated under reagan and died with him
asciilifeform: thinkingmachines co was another such. died same way.
asciilifeform: there is an entire graveyard of these; it simply so happens that i am only interested in the lispm-flavoured ones
asciilifeform: ( where i know for a fact that they Had Something )
asciilifeform: for all i know, the one and only path to e.g. a room-temperature supercon, was found at one of the reagan scamola firms, and died with it, also. i simply do not know about it.
fromloper: I also wanted to ask, did you figure out how to launch NS in VLM? I'm getting some Xlib error when I try to
asciilifeform: i suspect that the copy on the Official genera disk, never worked.
asciilifeform: but i never tried it under alpha, gotta try.
asciilifeform: and iirc phf has a working ivory -- worth trying there also
fromloper: I wonder if it's going to ask for a license key like Macsyma on the same disk does
asciilifeform: there is, theoretically, a working disasm
asciilifeform: fromloper: in re ivoryology, another unknown is the fep. virtually nothing is publicly known about the fep.
asciilifeform: ( for n00bz to the subj -- fep was an entire comp, mc68k, embedded inside bolix lispm, handled i/o and certain aspects of eggogology )
fromloper: Ivory still has mc68k?
fromloper: in its FEP
asciilifeform: afaik the standalone ones, did
asciilifeform: the 'macivory' did not, used a proggy running on the mac.
asciilifeform: ( a 68k mac.. )
fromloper: is VLM's life support built out of that proggy?
fromloper: http://archive.is/zw03T << Rainer Joswig speaks of some secret team maintaining the emulator, I wonder if he means http://btcbase.org/log/2017-08-21#1701489
a111: Logged on 2017-08-21 14:43 phf: i spent (mostly another whisperer and myself did) on getting vlm stable, and i'm unconvinced that some of the issues we encountered were purely "buggy vlm". there is, for example, a crash in floating point instruction that happens when you load document examiner on stock piratebay opengenera. i have no explanation for it still, because vlm code ~seems to do the right thing~. there are other similar instances
asciilifeform: fromloper: i actually do not know anything re who, if anyone, maintains. aside from phf's admission to having a private fork, linked above.
asciilifeform: ( last i knew, phf did not publish his changes )
asciilifeform: i do not know why not.
asciilifeform: this is a q that only he can answer, supposing he feels like answering.
fromloper: well, he doesn't for some reason
asciilifeform: re fp, i'll observe that bolix used a weitek fp unit
asciilifeform: similar in fact to the one in everybody's old 486
asciilifeform: and that if emulator's does not behave exactly same -- it will lead to barf, yes
asciilifeform: and who even knows if weitek is fully documented somewhere.
asciilifeform: ( for all i know, bolix relied on some undocumented behaviour of it. )
asciilifeform: fromloper: currently i suspect that many, possibly majority, of serious bolix collectors, ~do not want~ there to be an accurate emulator.
fromloper: I've read the whisperers discussion here, seems to be plausible
asciilifeform: i -- want. and this is why by and large they do not talk to me. they know about my www, they knew where to find me. they also know that i will publicly and immediately leak any bolixologial document that i am given. and want to make emulator. and for this, i suspect, they do not talk to me.
asciilifeform: this is a hypothesis. so far my best one.
asciilifeform: some people spent $10k's on their collections of bolixiana. and imagine that these will become worthless if an accurate fpgalogical emulator appears. and for all i know , this is true. i simply don't care.
asciilifeform: the ones who hoard secrets because they imagine that they have a ticket to being part of some future commercial revival of bolix, however -- those are idiots.
asciilifeform: there will be no second coming of commercial bolix.
fromloper: I'm curious what John C. Mallery intends to do with his property, other than collect support cheques
asciilifeform: i asked this q here years ago, and to this day have no answer of any kind.
asciilifeform: i suspect that there is no plan, the nsa cheques pay for his yachts and that's it.
asciilifeform: and when he dies they will pay for his sons' yachts. etc
fromloper: Kalman Reti said 4 years ago: "The problem is that the Symbolics IP is now owned by John Mallery; he has stated he has plans for making it available but so far (several years) has not yet done so."
asciilifeform: right, why would he. why give away yacht.
diana_coman: !!rate Covale` 1 euloran noob; found at least some of his way around
diana_coman: !!v 7AC227FA1D46917538127FAB0D4C5C45FF8064838BE08A92A589F00E4374C08F
deedbot: diana_coman rated Covale` 1 << euloran noob; found at least some of his way around
Covale`: diana_coman ty
asciilifeform: fromloper: if he gave it out, potentially someone else could bid on the support contract ( under american law, all contracts are theoretically publicly biddable . lockheed et al simply contrive to set up situation where no one else ~can~ perform a given contract )
asciilifeform: * all gov contracts
fromloper: asciilifeform: maybe he'll give up if something happens to DKS and Kalman Reti so he'll be out of people capable to do the job, both of them are rather old
asciilifeform: fromloper: i suspect not. because the 'support' is really ceremonial
asciilifeform: neither dks nor reti are really needed, to provide this 'support'.
asciilifeform: otherwise mallery would have long ago hired a 'spare' or two, and afaik he never has.
asciilifeform: the racket is not , as far as i can tell, intended to outlive the current participants.
asciilifeform: ( and if it is, it is by playing usg piano correctly, rather than by training replacement retis )
trinque: if so, how did folks this corrupt build anything worth having?
asciilifeform: trinque: by being 40 yrs younger, lol
fromloper: Mallery didn't do much for Symbolics before he bought it, outside of supplying it with CL-HTTP
asciilifeform: cl-http was notorious for its fuckyou-license
asciilifeform: but i'll admit that i know very, very little about mallery ( almost nothing is publicly known about him, he is an academic but not many publications in his name )
asciilifeform: what little clue there is, points to his having been an nsa asset since youth.
a111: Logged on 2014-03-21 04:58 mircea_popescu: understand that the most economic way to run the economy - now as during 1614 - is to just turn off all machinery, lock all warehouses and bury the key
diana_coman: http://btcbase.org/log/2018-01-13#1770368 <- mod6 did you publish this anywhere? it seems I might even have another test-case for it.. (version 99994 dies on it complaining that .vpatch is invalid)
a111: Logged on 2018-01-13 21:52 mod6: Lords and Ladies of The Most Serene Republic, I have created a blog post outlining the behavior changes in 99993. Please take a look and consider these changes. Let me know if you have any comments or questions! Thanks in advance. http://www.mod6.net/2018/99993/99993-changes.html
fromloper: Mallery's project at MIT: http://www.ai.mit.edu/projects/iiip/home-page.html
asciilifeform: 'This project ran from October 1, 1993 to October 1, 1997.'
asciilifeform: what he is being paid for TODAY, is not known afaik.
fromloper: he is talking at "cyber security" conferences
asciilifeform: d00d dun look so old. expect another 30-40 yrs of the dog sitting in the manger.
asciilifeform: 'Cyber space is an increasingly risky discourse and therefore will inevitably be securitised.' << exactly what i said: usg stuffed shirt.
asciilifeform: observe sponsor 'raytheon'.
fromloper: he's also on twitter, might nag him about it for laughs https://twitter.com/jcmallery_cyber
asciilifeform: why not also nag the statueofliberty, or washington monument.
asciilifeform: 'John Mallery @jcmallery_cyber 25 Dec 2017 Declinism is a psyop of adversaries...it was spread before during the Vietnam war.' << ahahahaha gold
asciilifeform: cheap nsa whore.
mod6: diana_coman: you mean the patch for 99993? yeah, i pasted it in here.... lemme look for it quick.
asciilifeform: hey fromloper , consider registering with deedbot ?
asciilifeform: fromloper: i'll rate you
fromloper: asciilifeform: alright, I'll do it
asciilifeform: amazing 'морда просит кирпича' on mallery.
asciilifeform: !#s face begs
asciilifeform: i was watching like usual with no audio. if anyone thinks i misses something thereby -- plox to write in.
diana_coman: uh oh, it seems asciilifeform's v misbehaves too: when pressing a leaf that has genesis as antecedent it presses ALSO all other descendants of genesis from what I can tell
asciilifeform: diana_coman: it does, this was discussed.
asciilifeform: afaik the only correct vtron currently existing , in this respect, is phf's.
diana_coman: ah, I missed that then, I thought yours was grabbing leaf by leaf too
asciilifeform: nope. phf afaik has the 1 and only mechanically-correct vtron. mod6 has a prototype of the 2nd.
asciilifeform: ( i have not tried yet )
diana_coman: k, I'll try that as soon as mod6 finds the patch
mod6: how do i search the logs for all the lines that I have said?
trinque: !#s from:mod6
diana_coman: mod6, from:mod6 ?
diana_coman: ha, super-fast trinque !
trinque blows on keyboard
mod6: ooooh, i was doing "from: mod6" and getting very strange results.
diana_coman: yay, thank you mod6 !
mod6: np. use that to patch 99994.
mod6: up to 99993
diana_coman goes to try
fromloper: I'm going to join as amberglint now
trinque: !!up amberglint
deedbot: amberglint voiced for 30 minutes.
deedbot: A7E708351AF14BB5C8B48DA323264C245A4563B8 registered as amberglint.
diana_coman: apparently patch worked, v reports now new version
trinque: !!v A52E78CBF699C414F662B5E4849A1D843B5BB7B0FF282D1AD0622FEC36560AF5
deedbot: trinque rated amberglint 1 << new blood
trinque: amberglint: try to self-voice in pm with deedbot now
asciilifeform: !!rate amberglint 1 bolixologist
asciilifeform: !!v C119442E4976802D6E83E0D0AFA77098FD4FCB02AEAB5DC0DC965DCBF0A748B2
deedbot: asciilifeform rated amberglint 1 << bolixologist
amberglint: it's working, thank you
asciilifeform: welcome, amberglint .
asciilifeform: amberglint: want to say a bit re where you came from, how you found asciilifeform's www, etc ?
asciilifeform: ( or found #t first ? or other ? )
shinohai wonders if he should rate ben_vulpes as "bollocksologist" due to his recent trap encounters .....
amberglint: asciilifeform: I can't remember how I found your www, I'm reading it since 2012 or so; I found trilema.com from one of your articles
amberglint: I'm a software engineer, live in Russia
amberglint: I was reading the logs for a while, thought about joining you earlier but felt a bit intimidated to be honest
asciilifeform: amberglint: i assume you already know about the log ( btcbase.org/log & elsewhere ) then.
amberglint: btcbase.org is the logotron of my choice
asciilifeform: it was made by phf , address all complaints to him!1!
amberglint: haven't had any issues with it, it's very handy
asciilifeform: it is.
asciilifeform: phf also from ru; and iirc so is apeloyee; asciilifeform from old su but marooned in usa; mircea_popescu speaks (more than he is willing to admit, lol) ru; possibly other folx, tuned in but still lurking, also.
amberglint: yeah, I caught almost everyone ru-speaking in the logs though I didn't know about apeloyee
asciilifeform: he's a very clever maths d00d. logs in every other week or so, nitpicks re fine points of ffa.
asciilifeform: since iirc july of '17 or so.
asciilifeform: !!born apeloyee
asciilifeform: !#born apeloyee
a111: 2017-09-13 <apeloyee> would O(N^2) modular multiplication be too slow?
asciilifeform: sept. apparently.
asciilifeform: but iirc he existed as a 'fromloper' prev.
asciilifeform: !#s from:fromloper ffa
a111: 0 results for "from:fromloper ffa", http://btcbase.org/log-search?q=from%3Afromloper%20ffa
amberglint: plenty of math-educated people here
asciilifeform: (possibly he had other temp name, i cannot now recall.)
asciilifeform: aha. mircea_popescu also at one time was a maths man.
asciilifeform: and diana_coman , and possibly others.
asciilifeform: and i know of at least 1 still-lurking d00d, who was. and who knows who else.
amberglint: asciilifeform: have you read "Digital Design and Computer Architecture" by D. and S. Harris? I'm using it (in ru print translation) as my hardware handbook and I'm curious if you have any opinion on it
asciilifeform: i have an old 'for india' eng edition here.
asciilifeform: unremarkable schoolbook; slightly better imho than hennessey's
asciilifeform: i do not like vhdl; and do not see the point of 'systemverilog' (vs classical); but these are my personal prefs
amberglint: btw, one of Ivory and NS designers, Neil Weste, wrote his own schoolbook: http://pages.hmc.edu/harris/cmosvlsi/4e/index.html
amberglint: with the same Harris
asciilifeform: amberglint: do you have it ? anything unusual, ivoryistic inside it ?
asciilifeform: the demo chapter seems to have a very, very detailed discussion of machine arithmetic.
asciilifeform: with quite recent lit cited.
amberglint: asciilifeform: I have a pdf somewhere, a quick look didn't notice anything Ivory-specific
amberglint: it should be on gen.lib.rus.ec
asciilifeform: i have a similar item , http://btcbase.org/log/2017-05-16#1657241 , it proved to be of very, very limited help for ffa , the constraint of the pc arch limits the use of fancy adders etc
a111: Logged on 2017-05-16 22:10 asciilifeform: unrelatedly, 'finite precision number systems and arithmetic' (kornerup & matula, cambridge press) is mega-b00k, the only one i've found on subj that is NOT a mere plagiarism of knuth, has useful algos for e.g. carry-free ops, hardwarizations
asciilifeform: ultimately i ended up using nothing at all from it.
asciilifeform: but if i were designing asic -- yes, would use.
asciilifeform: and weste's , too. it seems to contain many usable goodies for asicist.
asciilifeform: unfortunately i do not have any way to make asic. as for fpga, none exist of the necessary size. ( see e.g. http://btcbase.org/log/2018-01-04#1764242 )
a111: Logged on 2018-01-04 20:06 asciilifeform: in other 'news', it is apparently impossible to fit even ONE 4096-bit adder into an ice40-8k ( the largest in the series )
amberglint: asciilifeform: do you know what this language is? http://users.rcn.com/david-moon/MMD/MMD.lunar looks like Moon's own invention
asciilifeform: amberglint: PLOT ( http://users.rcn.com/david-moon/PLOT/ , http://users.rcn.com/david-moon/PLOT3/ . )
asciilifeform: seemed to me, to be an infix lisp, sorta like 'dylan'
asciilifeform: ( why he did this ? i do not know )
amberglint: he renamed it to Lunar, apparently
amberglint: no one else seems to know or care about it, judging by google's output
asciilifeform: i read the linked manual in '08 and will admit that i did not find it very interesting. it is the same kind of dead end as dylan.
asciilifeform: ( and if anyone began to use it, would prolly end as same kind of catastrophe as e.g. ruby . )
deedbot: http://www.loper-os.org/?p=2146 << Loper OS - Rodenticide with the Seiko DPU414 Tape Printer.
mircea_popescu: you know ftr trb node state of blockpool has improved tremendously.
mircea_popescu: cool deal.
asciilifeform: and ohai mircea_popescu !
asciilifeform: saw any crocodiles ?
mircea_popescu: actually... just macaws. lots and lots and lots of macaws.
danielpbarron: !!rate TomServo 1 fg customer
mircea_popescu: http://btcbase.org/log/2018-01-17#1771636 << i have nfi what a binace is and i see no problem with random numbers fiatists assign to bitcoin fluctuating ~randomly.
a111: Logged on 2018-01-17 11:06 Techman: mircea_popescu: what isy our take on bitcoin dropping below 10K (at least on binance)
mircea_popescu: o check it out asciilifeform "cardano" the coin is up 25%!!1
mircea_popescu: "WORTH ALMOST TWO BILLION"!!11
asciilifeform: how is mpexcoin doing tho.
asciilifeform: and bbeterium.
asciilifeform: haskell no less
mircea_popescu: "Cardano is a decentralised public blockchain and cryptocurrency project and is fully open source. Cardano is developing a smart contract platform which seeks to deliver more advanced features than any protocol previously developed. It is the first blockchain platform to evolve out of a scientific philosophy and a research-first driven approach. Thedevelopment team consists of a large global collective of expert engineers and
mircea_popescu: http://btcbase.org/log/2018-01-17#1771642 << i don't see a problem with it necessarily, but it's not clear what may hide under rock #2. try and see i guess ?
a111: Logged on 2018-01-17 13:09 esthlos: http://btcbase.org/log/2018-01-16#1771055 << My thought was to scrap the current client in favor of a customized one, with eucrypt protocol as the backbone. Is this 1. not what you want, or 2. a bad idea?
asciilifeform: 'The registered office of Cardano Foundation is: Cardano Stiftung, Gubelstrasse 11, 6300 Zug, Switzerland.' classy.
mircea_popescu: asciilifeform gotta have a foundation like tits gotta have a boar.
mircea_popescu: crypto ag is zug-erstrasse, 6312 gubel, swizerland.
mircea_popescu: geddit ?
asciilifeform: holyfuq it ACTUALLY is..
asciilifeform: pretty great.
asciilifeform: a+++ trololol
mircea_popescu: they just play trivial pursuit see.
mircea_popescu: or what's the one with the mixing.
mircea_popescu: o right. SYMMETRICAL CIPHER.
asciilifeform: to think, somebody sat, sewed this.
mircea_popescu: http://btcbase.org/log/2018-01-17#1771644 << nah not at all. just proposed what might've been an easy entry point. you dun like it you dun have to.
a111: Logged on 2018-01-17 13:15 esthlos: Rereading, seems clear that you want eulora's graphics engine.
asciilifeform: previously i had it filed under perlisms.
mircea_popescu: asciilifeform it rather looks like the elaboratest trollcoin so far.
asciilifeform: afaik gold star champion , aha.
mircea_popescu: oh, damn, remember days of GoldStar
a111: Logged on 2018-01-17 15:30 asciilifeform: has apeloyee found a specific instance where it can be made to eggog ? or is this a hypothetical 'once less clueful people start changing things' observation ?
mircea_popescu: http://btcbase.org/log/2018-01-17#1771717 << this is a great win, i'm glad he stuck with it.
a111: Logged on 2018-01-17 15:33 asciilifeform: really all routines oughta behave consistently in re input-overwrite.
mircea_popescu: saying "well i can't protect car from usage of idiots" is one thing, but having the gas and break pedals not ever interchange is the other thing.
a111: Logged on 2018-01-17 15:39 apeloyee: does gnat provide a facility to check aliasing at runtime?