asciilifeform: blew most of an hr looking for that dumper ('gotta be in there...')
asciilifeform: hey mircea_popescu , do you remember whether gpg 1.4 ( virginal ) can be forced to dump hashpayload when verifying sigs ?
asciilifeform: possibly one of the contemporary calcs with 'basic' ( e.g. http://calculators.torensma.net/files/images/sharp_el-5400.jpg )
asciilifeform: PeterL: the result is that the only way for PeterL to use something asciilifeform wrote, is to turn his house into an exact duplicate of asciilifeform's; or alternatively to cut-and-paste, eulora-mpi-style, destroying all record of the copied item's history. but i already said this. try reading log ?
asciilifeform: PeterL: as the original ( and afaik to date the only ) perpetrator of this particular warcrime ( the shiva item specifically ) i will say , imho the solution is to Not Do That . rather than to try to make it mechanically impossible. but i'ma not repeat this point further, it dun help .
asciilifeform: https://archive.is/gDphe << meanwhile, in other noose, '...impact on CPU usage of one of our back-end services after a host was patched to address the Meltdown vulnerability...'
asciilifeform: rrything into 1file. this comes at a cost. apparently this particular electric fence must get pissed on empirically, for the cost to become obvious. let it be pissed on then, i haven't presently anything to add.
asciilifeform: http://btcbase.org/log/2018-01-06#1765921 << this is entirely troo tho. i simply dun see that it is amenable to a mechanical solution.
asciilifeform: http://btcbase.org/log/2018-01-06#1765881 << sanity looks like this : 'trb since 2015 is made of v. and works. and quite compact. and fundamentally mechanics are correct.'
asciilifeform: and there is no 'ambiguity' in 2015-v , except in so far as incompetent patch authors permit it.
asciilifeform: and now it takes a lifetime to simply juggle the v-mechanics, leaving ~0 time for any of the 'irrelevant' detail like, say, writing ffa.
asciilifeform: ... and i recommend then to dispense with the pretense of automation, and simply return to signing tarballs. moar honest, and logically equivalent.
asciilifeform: daily dope is simply a black hole for money, even if it dun do you in
asciilifeform: if you have a record of all the prev shots, it is trivial to avoid recurring ( use simple counter )
asciilifeform: they're simply 'i want a piece of shit that won't recur'
asciilifeform: and come to think of it, damn near any eng trans of substantially complicated philosopher
asciilifeform: this is what distinguishes us from the apes, we can do experiment, rather than argue over empty table.
asciilifeform: i'ma summarize the v thing : if you have a proposed new v algo ; and it would turn my 1kB patches into 1MB, and my readable 3 lines into 100kLoc of ?#@%$*(@%% , and my trivial machine-diff-verifiable changes into 'why dontcha sit for 5 years doing eyeball-powered diff' -- it is NOT an improvement. and i won't touch it. sign it. sign anything made on it. etc
asciilifeform: and is SIMPLE .
asciilifeform: take for example http://btcbase.org/patches/asciilifeform_maxint_locks_corrected . in properly working v, it ONLY depends on db.cpp being a particular hash . and does NOT lock you into anything else being anything else in particular.
asciilifeform: that it completely thermonukes the usefulness of v, to me personally.
asciilifeform: and imposes nonsensical constraint that would not otherwise be imposed.
asciilifeform: just like how, e.g., asciilifeform_and_now_we_have_eatblock coalesces mod6_fix_dumpblock_params and asciilifeform_ver_now_5_4_and_irc_is_gone_and_now_must_give_ip
asciilifeform: ( what we have right now, is that we have no 'if-clause' or 'else-clause', physically, they are exactly the same thing, simply happen to be a pair of'em )
asciilifeform: this is an engineering tension, ben_vulpes ; i'll grant that the trailing _ is ugly. however it makes the mechanism simpler, all { are handled in exactly same way, and ditto all }
asciilifeform: see, asciilifeform's orig trick with tmp was ~specifically~ to abolish the gpg keyring nonsense
asciilifeform: user should not have to look in tmp.
asciilifeform: for so long as vtron uses gpg shell-out, it's stuck with the tmp dir crapola
asciilifeform: ( thinkaboutit, tmp would be entirely useless if this were not so )
asciilifeform: mod6: it makes, e.g., parallelly running vtrons on same box, impossible
asciilifeform: mod6: the most serious bug is not even the failure to delete the tempdir, but that every run of the vtron uses ~same one~
asciilifeform: do you now have a comp and able to work ?
asciilifeform: gabriel_laddel: didja ever download the 1GB example FG bin ?
asciilifeform: and anyone who dunlike it , can jump in a lake.
asciilifeform: or for that matter any record kept of old instructions , that the thing could jump to ?
asciilifeform: so ben_vulpes do you see a jump ?
asciilifeform: bbbut noooo, gotta reorder, because Only A Terorrist Would expect microshit to write sane compiler...
asciilifeform: semantics-changing optimization belongs in ~compiler~ (if even there), not in iron.
asciilifeform: temp dir paths gotta be gensyms.
asciilifeform: mod6: what's make_tmpdir made of ?
asciilifeform: let's quote ftr : 'Creates a temporary directory in the most secure manner possible. There are no race conditions in the directory’s creation. The directory is readable, writable, and searchable only by the creating user ID. The user of mkdtemp() is responsible for deleting the temporary directory and its contents when done with it.'
asciilifeform: https://docs.python.org/2/library/tempfile.html << gory details.
asciilifeform: however the external 'tempfile' item, made gensymtronic dirs. so this never became a headache.
asciilifeform: did not attempt to catch ctrl-c or any other signal.
asciilifeform: .... shutil.rmtree(gpgtmp)
asciilifeform: gpgtmp = tempfile.mkdtemp()
asciilifeform: ... used 'tempfile' py lib
asciilifeform: mod6: the temp dir is primo example of an always-ok-to-kill item. i.e. one which the vtron run itself created and would never otherwise exist
asciilifeform: or at the very least not ever use the same absolute tmp path
asciilifeform: nah the tmp thing definitely ought to clean up
asciilifeform: rather than simply ignoring inputs.
asciilifeform: it comes with the binariolade gnat. if you're using gcc gnat, will have to compile it, a little bit gnarly.
asciilifeform: http://btcbase.org/log/2018-01-05#1764882 << i'm quite tempted to give the archive another combing and make a sequel to my http://www.loper-os.org/?p=165 item
asciilifeform admits that he does not particularly ~like~ emacs. it simply ended up a schelling point, like linux. but suffers from same type of problems.
asciilifeform: most 2048bitness state is composite
asciilifeform: the described item is trivially impossible
asciilifeform: oh it's simply a painfully small cpld is all
asciilifeform: i.e. if function call simple, i.e. fits on 1 line -- then 1line; if not -- then 1 arg per line.
asciilifeform: pretty good example
asciilifeform: the memory gymnastics in mpi. and 'for your convenience, we will package the defective transistors separately!11' , i'll call it here
asciilifeform: not that it's a bad example, but 'human rights' is 'easy' bunkum , unlikely to be confused with a physically-existing item except by the deliberately mendacious folks and their useful idiots
asciilifeform: the pantsuit picture is then presumably that somebody 'sat down to impose epicycles' ( in the spirit of 'newton sat down to...' ) ?
asciilifeform: again secondarystack is not implemented as an open-ended (unboundedly growing) item
asciilifeform: presumably was done to implement 100% of the standard.
asciilifeform: inefficiency are bad for Lisp, which would have done it a lot better had it been in control, but GUILE doesn't do it any better. GUILE combines the worst of both worlds, in an attempt to bring the best of one world to a world where it doesn't really belong. on top of this, it's Scheme, and it's expensive to run, there's so much wrong with it that nobody can use it without fixing some part of it. so, it's going to be a winner, but
asciilifeform: and, to round off the archaeological dig, https://www.xach.com/naggum/articles/3129467830883882@naggum.no.html >> 'the programming environment model in Unix is an imitation of the Lisp machine, and the way it is implemented is through processes and inter-process communication instead of function calls. functions in the Lisp heap are programs on disk in the Unix model. the optimizations that made Unix able to survive this incredible
asciilifeform: ( this is almost possibly the first litmus for a n00b : will he read logs when told to ? show symptoms of actually having done so, and learne d? )
asciilifeform: ReadErr: when you 'download proggy from shithub', it is exactly same act as if you could, in a restaurant, order '1 cubic litre from public dump' as a dish. complete with whatever happens to be scopped out, used condoms, syringes, rotten vegetables, dead rats
asciilifeform: ~all ffa ops can be reduced to 'add-with-possible-2scomplement' and 'shift'.
asciilifeform: in other 'news', it is apparently impossible to fit even ONE 4096-bit adder into an ice40-8k ( the largest in the series )
asciilifeform: 'My conclusion from the interaction is that, now more than ever, when it comes to future collaborators, in any context, it is important for anyone for whom justice matters to probe candidates deeply for fascist tendencies. If they show a sign, pass. Anti-immigrant, anti-woman, anti-queer, and anti-black behaviors and actions often correlate: if you see one sign, often there are more underneath. Even if the person claims to value egal
asciilifeform: why am i reading about e.g. '...ignorance about the lived experience of women compiler writers, say, can lead to hurtful behavior...' ?
asciilifeform: details proclaimed uninteresting -- get de-emphasized
asciilifeform: to borrow BingoBoingo circa 2014 -- the correct solution to fat is... not to become fat; rather than 'reach implements' and double-wide train seats
asciilifeform: right, his algo follows 'dump truck' model. my orig one -- did not, it did exactly as mircea_popescu describes.
asciilifeform: turning a dump truck full of ???!?$$??? that you found on the street, that contains some parts valid v-sigs, patches, and some parts chicken shit -- into a purely valid v-tree , is o(n^2). but q is why to permit the dump truck situation to begin with.
asciilifeform: mircea_popescu: whole day sawed, chopped -- but could not fix the comp !
asciilifeform: ReadErr: are you familiar with the relationship between bitcoin and the empire ?
asciilifeform: ^ boatload of funstuff concerning , e.g., rng testing methodology; rigorous approach to stego; novel attacks on symmetriccipherolade; various other interesting ( and quite compact ) items.
asciilifeform: i'ma have to eat the 'not bias!' answer. even tho it leaves me without a clean analysis-flavoured picture of why successive rounds of faircoin improve entropy metrics across-the-board (regardless of what litmus is chosen)
asciilifeform: in other verymuch nonnews, asciilifeform for some reason only today realized that von neumann's fair coin algo is simply 'numerical differentiation' for discretes, and removes bias for the same reason differentiation removes constant
asciilifeform: the ones asciilifeform slept in at uni dorm were jumpable-IN as well as out
asciilifeform: the proximate cause of death was, reportedly, the discontinuation of the jp micropower 68k and accompanying chipset, as that atlantis sank. and not replaced.
asciilifeform: ben_vulpes: i've always liked ~good~ pocket calcs. ( not as a comp replacement, or a head replacement, but exactly as a 'tactile arithmetization' plaything. ) but no good ones have been made in decade+ or i expect ever will be again.
asciilifeform: prolly cheapest pill is simply to sit it down behind znc
asciilifeform: 'If we look at overall results, the fastest machines are ancient. Newer machines are all over the place. Fancy gaming rigs with unusually high refresh-rate displays are almost competitive with machines from the late 70s and early 80s, but “normal” modern computers can’t compete with thirty to forty year old machines.'
asciilifeform: and when you impose the condition that it MUST -- you end up with...
asciilifeform: for completeness i'll mention the denoument:
asciilifeform: in train, story went -- pumping.
asciilifeform: train car is built to resist noncoherent bumps. not idjits pumping its resonance.
asciilifeform: it isn't a physical impossibility, petrol trucks have overturned from 'slosh' effect
asciilifeform: if so lazy that won't bother to 'dip them' -- then yes, not complete
asciilifeform: just as mouse without white cells ain't complete mouse.
asciilifeform: evidently not complete
asciilifeform: that's the key, them folx were never 'complete country'
asciilifeform: ( and most of the remainder -- the old, the female, the diseased, the zeks who did 0 soldiering, attempted or otherwise )
asciilifeform: BingoBoingo: if you wanted to do this for real, vs. gabriel_laddelization, cost is roughly comparable to a moon flight.
asciilifeform: 'With the page table splitting patches merged, it becomes necessary for the kernel to flush these caches every time the kernel begins executing, and every time user code resumes executing. For some workloads, the effective total loss of the TLB lead around every system call leads to highly visible slowdowns: @grsecurity measured a simple case where Linux “du -s” suffered a 50% slowdown on a
asciilifeform: selective disclosure of 0days to benefit empire -- same as any other wetwork for empire
asciilifeform: linked strictly for the responsibledisclosurism cancer implicit in any such embargo.
asciilifeform: in other heathen lulz, http://archive.is/QmV5G >> 'there is presently an embargoed security bug impacting apparently all contemporary CPU architectures that implement virtual memory, requiring hardware changes to fully resolve'
asciilifeform: 'I did publish, separately in sci.crypt, a nostalgic piece about a possible ancestor to this system. You can't very well accuse me of claiming novelty. There is a lot of deviousness and a bit of intelligence in what I proposed, but the novelty is in the way I implement the idea, and in the beneficial side effects.'
asciilifeform: gpl, for instance ( ignoring for a moment that it has 0 to do with computing ) was created by moglen
asciilifeform: gotta luvv 'improperly destroy the economic value' phrase
asciilifeform: 'March 7, 2003 - The SCO Group filed legal action against IBM in the State Court of Utah for trade secrets misappropriation, tortious interference, unfair competition and breach of contract. The complaint alleges that IBM made concentrated efforts to improperly destroy the economic value of UNIX, particularly UNIX on Intel, to benefit IBM's Linux services business.'
asciilifeform: prolly mircea_popescu is right and pyramid long empty
asciilifeform: meanwhile, in vintage lulz, http://countercomplex.blogspot.com/2014/08/the-resource-leak-bug-of-our.html
asciilifeform: bus is a poverty artifact. and i will add that , most hilariously, recent items like pcie are actually implemented as ports, physically! but on the idjit x86 end EMULATE behaviour of bus !!
asciilifeform: trinque: i still haven't attempted musltronic gentoo. ( and have nfi whether it could be used on a workstation, say -- does emacs run ? what dies ? )
asciilifeform: asciilifeform for example has >decade of tarball archive
asciilifeform: the 'holy grail' is items which are demonstrably safe to operate continuously -- i.e. fsa with no wedge states. these are not so easy to achieve; FUCKGOATS is one example
asciilifeform: sbcl is a pretty interesting example of one of those spiked pits, like e.g. gcc -- items to which there is no practical alternative except 'throw away the comp and build log cabin'. but asciilifeform does not have phf's deep historical view of sbcl/cmucl ; asciilifeform arrived into the spiked pit directly
asciilifeform: ( asciilifeform , like complete idiot, went and thought... 'i can make a useful diagram! with svg ! which exists!' )
asciilifeform: it was a whole majorversion of sbcl that simply won't usocket..
asciilifeform: would rather magic it away. like in microshit's ciphered patches. ( i knew folx who made a comfortable living simply by reversing those. )
asciilifeform: ( this is prolly doomed to happen in the end. i.e. gotta retarget gnat to a simplified mips or the like, and then run in emulator, verify actual clock cycle counts )
asciilifeform: consider the approach in ffa. only critical bottlenecks, that soak up 90+% of cycles and create an impractically-slow rsa op , get massaged ~to the extent necessary~ , and without compromising type safety
asciilifeform: http://btcbase.org/log/2017-12-29#1760637 << hilariously, i had previously read the whole thing... on fcc's www. ( they have a public pillory of all citations/fines/complaints/etc )
asciilifeform: with example in, out
asciilifeform: e.g. 'spaces muchly less important than printables'
asciilifeform: http://btcbase.org/log/2017-12-29#1760185 << it is unreasonable to ask ~machine~ to enforce intellectual discipline. machine cannot do this, it's an 'ai-complete' problem.
asciilifeform: but why not see empirically:
asciilifeform: phf: i came up with it in 2016 when wrote the orig, unpublished mpitronic 'p'
asciilifeform: ( emphasis on past tense )
asciilifeform: imho this is aesthetically displeasing but inevitable, eventually it'll be this or copying disks, sync-from-empty-space will be impractical in human timeframe
asciilifeform: nao, if we reintroduce checkpoints ( SANE checkpoints : i.e. keccak-of-whole-block-bitwise, rather than merkleism and sha2; and pgp-signed config eaten at boot ) we can have nodes that sync from empty hdd to full in <1day ...
asciilifeform: ( in particular the orphanages amputations. good chunk of bandwidth is TO THIS. DAY. wasted , by prbtrons throwing their liquishit at trbtron )
asciilifeform: ( and , consider, if mining were not also a bug, who would waste any time attempting to converse with prbtrons ? )
asciilifeform: http://btcbase.org/log/2017-12-28#1759898 << in a sane gossiptron, nobody'd be keeping bastard blocks around to begin with, and the problem would not even be formulatable, 'what do you mean, out of order, everybody's got an ordered array of blocks, some people simply longer one than others, let's all visit'em'
asciilifeform: ( i suspect an attempted overflow exploit, against something-or-other )
asciilifeform: simply because apparently 'no demand'
asciilifeform meanwhile was watching zoolag sync, 'hmm 10min from nao' turned into hour+, and still 10blox behind. culprit seems to be a combo of 'everybody else is lagging' and 'flooded with mempool crud, and as result , not spending enuff time disconnecting unproductives and pushgetblocks()ing with novel peers'
asciilifeform: ( or simply failed to reach takeoff velocity )
asciilifeform: afaik phf is currently the all-star champ from that group
asciilifeform: 'motherfuckers, i gave then such particle-like electrons, and they STILL dun have roomtemp supercon...'
asciilifeform: phakt : plenty of 'next steps' that apparently too tall. e.g. roomtemp supercon.
asciilifeform: tomato for petrol. but today imports both from eu. because spread legs for nato.
asciilifeform: it was always -ev, simply not on short enuff time scale.
asciilifeform: they... do. simply takes a while.
asciilifeform: meanwhile, in an apparent imitation of http://btcbase.org/log/2017-12-12#1749817 : http://destery.info/cidal/mpex-bitcoin-nupe.php <<< aaaaand, very similarly, returns ENTIRELY different turd to archive.is. orig. screenshitted, http://www.loper-os.org/pub/mpex_flavoured_spamola.jpg for posterity.
asciilifeform: phf: apparently lamport missed this memo
asciilifeform: at the very least could've emphasized the absence of a successor.
asciilifeform: entirely possible that the man's chief sin was simply the failure to find worthy successor. he left tex to the maggots, and the result is exactly the typical result. ( just as e.g. stalin ended up leaving his 'tex' to the maggots, with similar result )
asciilifeform: ( and i gotta wonder whether lamport himself was an active perpetrator, or passive victim similar to knuth himself, when the 3GB of liquishit began to form )
asciilifeform: the interesting bit is that this disconnect, 'can use ipad but still do honest mathematics', doesn't show any serious symptoms of existing
asciilifeform: i get it, in the 'organic' system that is a live p2p net, proper controlled experiments are quite impossible. this however does NOT mean that one oughta freely give in to urge to climb back up the tree, becoming a monkey again, and think in voodoo criteria. even if the circumstances heavily encourage this , by failing to reward rational thought ( see mircea_popescu's thread with the italian fishermen !! , http://btcbase.org/log/2017-
asciilifeform: so that questions like 'did it even have net access for that week', to 'has it ASKED anyone for the next block, or just sat there with mouth open? ' and 'did anyone ANSWER, when asked, or just shat forth mempool crapola and bastards 50 blox ahead' can be answered.
asciilifeform: as for nodes at the 'tip', the path of chinesium through layers of prb is a lottery, and i suspect that attempting to measure the effect of a trb patch on said behaviour is doomed to astrologize over noise
asciilifeform: shiva series was imho great example of 'coarse error in pilotage' re this thread
asciilifeform: the usg polizei prioritize the voice pirates, because they compete directly with the usg 'music' monopoly
asciilifeform: http://btcbase.org/log/2017-12-26#1758601 << queue is empty
asciilifeform: in other noose, asciilifeform discovered that it is impossible to use trinque's bot on fleanode if connecting from a shitazon session:
asciilifeform: funnily enuff, the absolute all-time champ at never-lagging in asciilifeform's house of horrors is... an ancient (circa 2013..?) prb !! e.g. currently at 500849
asciilifeform: it isn't even impossible that there's only been 1 block in past 2hrs, say
asciilifeform: !~later tell trinque http://wotpaste.cascadianhacker.com/pastes/nxnWA/?raw=true << or for that matter anybody else using trinque-bot -- any idea what gives ? i followed the example in the readme...
asciilifeform: 'blockchain'ism is simply a very expensive means of approximating a solution to this problem.
asciilifeform: 1 way, would be by going to his own cellar and fetching optical disk where he has ~his~ mpi
asciilifeform: it is possible that it will improve block reception at the expense of outgoing tx propagation.
asciilifeform: ( and can't simply use the html escape notation, because it gets literalized by the code-formatter )
asciilifeform: i'ma prolly have to rewrite the code-formatter plugin thing, it insists on autoprocessing to emplace the escapes, but does not do ~mismatched~ double-quotes
asciilifeform: http://btcbase.org/log/2017-12-24#1757842 << the wp 'code' plugin is massive headache, i've been fighting it since ch1 . ( e.g in ch4 i had to replace the " in ('"') with a similar-looking uniturd, because double-escape is apparently impossible )
asciilifeform: ( that , e.g., barrierizes reads correctly, rather than blocking completely )
asciilifeform: ( funnily enough it is now virtually impossible to connect to, on account of actually getting fed a block ~every time it touches anybody ... )
asciilifeform: this is testable empirically; like-so: any N trb nodes built with 'aggression' patch above, and linked via 'wires', should never fall out of height-sync with one another by more than a coupla blox. at any point.
asciilifeform: !~later tell trinque where didja get the log-timestamps in your trb ? ( which patch pressed to ? )
asciilifeform: http://btcbase.org/log/2017-12-23#1757625 << lol i'ma guess mircea_popescu ended up in pediwik swamp when looked for gears...
asciilifeform: mircea_popescu: lol, and when chinese mp3trons did better job, with 0 proprietary crapware needed to mount, and for 1/5th the price..
asciilifeform: b/w object that is imperfect because of limitations of the materials, and one that is broken because of limitations of the designer, who was dropped as a child
asciilifeform: mircea_popescu: physically, known-imperfectly tho. rather than 'js soup'-imperfectly.
asciilifeform: it was the kompyooting of its time. except : actually worked...
asciilifeform: i have not yet attempted a musltronic one.
asciilifeform: http://btcbase.org/log/2017-12-23#1757327 << the important bit ( and iirc i emphasized this in the lamport piece ) is to agree IN ADVANCE
asciilifeform: nope. for instance university plankton are stateemployees
asciilifeform: complete with pile of c macros
asciilifeform: mpi_tdiv_q_2exp is in fact used in primegen.c , but in such a way that its brokenness doesn't affect the output , 'accidentally'
asciilifeform: grep for q = mpi_copy( nminus1 );
asciilifeform: but instead implementing the Troo Algo.
asciilifeform: and compiles pretty cleanly.
asciilifeform: for those annoting little cpubound problems like hbomb implosion contours etc
asciilifeform: really the endgame of this is 'compile to fpga'
asciilifeform: 'compile to c'
asciilifeform: 'compile to fortran'
asciilifeform: ( i assume it also sheds various mempoolisms ? )
asciilifeform: theoretically a miner who gives a damn re max rake, oughta tune in when if e.g. mircea_popescu were to pump out a fat tx on sw.
asciilifeform: afaik it's entirely impossible without rotting iron
asciilifeform: aha, mempoolism
asciilifeform: you gotta compare without reset tho.
asciilifeform: iirc recent prb ( as analyzed by jurov, still digging for the thread ) will simply drop you if you connect and report <0.7 .
asciilifeform: if it in fact has become impossible to get a tx out without emulating all of prb, we have a Problem
asciilifeform: much of what the 'power rangers' did to their bitcoin, was an elaborate dance around this problem, with a dozen pseudosolutions that guzzled memory, and -- more importantly -- destroyed the integrity of their sync ( the orphanage bullshit, the headers-first bullshit , etc )
asciilifeform: it sits on the edge between outright wrecking and simple down's syndrome
asciilifeform: just as easily it is possible to give it a 'here's an empty string of length L to take a shit into, for each cmdline param, and if the actual exceeds it, trigger constrainterror'
asciilifeform: especially a compiler.
asciilifeform: c is simply a terrifyingly retarded lang in which to write ~anything~ compactly, even ccompiler.
asciilifeform: incidentally bellard's tcc is not in any simple way trimmable, no autoconf garbage or the like, in there.
asciilifeform: and of comparable size to... minix
asciilifeform: quite heavy compared to even, say, trb.
asciilifeform: only 'small' compared to gcc monster.
asciilifeform: ( b/w a fits-in-cache interpreter, and sbcl's compiler )
asciilifeform: the existence of the compiler seems to be ~the~ fountain of braindamage for pc lisps
asciilifeform: in other noose, asciilifeform found it impossible to rebuild http://btcbase.org/log/2017-12-20#1755200 under gcc 4.9
asciilifeform: phf: i also tried this, ~decade ago, quite impossible
asciilifeform: i mean, it never before existed in gentoo, it's apparently an imported debianism.
asciilifeform: 'The GNU C++ team works hard to avoid breaking ABI compatibility between releases, including between different -std= modes. But some new complexity requirements in the C++11 standard require ABI changes...' motherfuckers
asciilifeform: if the sync behaviour weren't so atrociously retarded, this'd be a pretty simple thing
asciilifeform contemplates placing trb on ramdisk on this box
asciilifeform: and, moar importantly , wai
asciilifeform: mpi_size_t _i; \
asciilifeform: #define MPN_COPY_INCR( d, s, n) \
asciilifeform: mpi_size_t _i; \
asciilifeform: #define MPN_COPY_DECR( d, s, n ) \
asciilifeform: MNP_COPY_INCR we find in include/mpi-internal.h , and is a straight memcpy-style copier.
asciilifeform: work it out : limb_cnt will be 0 ; the inner if takes the 'else' branch; MPN_COPY_INCR(w->d, u->d , u->limbs ) is the resulting call
asciilifeform: ( replacing 'mpi' with 'mpz' )
asciilifeform: 9 out of 10 times you can find clue re what an mpiism was, by looking in'ere.
asciilifeform: diana_coman: https://gmplib.org/manual/Integer-Division.html has the goodz. they renamed it , tho, mpz_tdiv_q_2exp .
asciilifeform: i wouldn't propose to translate it for public consumption, no
asciilifeform: and can compute using match sticks
asciilifeform: then failed to procure the box, or a usable display for such, and promptly stoppedconsidering
asciilifeform: ( winblowz, as most-everyone knows, won't boot off an actual read-only device. so these steampunk hacks. )
asciilifeform: you wouldn't want chumper to install from cd ( they dun give'im a cd, in any event )
asciilifeform: the 'ancients' , notably, were obsessed with 'can haz search'. recall vannevar bush's elaborate 'steampunk' schemes for optical/analogue search in text
asciilifeform: but pre-mechanization log is of quite limited use compared to current item.
asciilifeform: but , importantly , nuffin since
asciilifeform: if all yer workingsets fit in yer cache -- thank molloch, sure , no cause for complaint.
asciilifeform: 'what kind of constraint difftrons may impose' ?
asciilifeform: mircea_popescu: this goes all the way to the fact that we dun actually ~understand~ rsa ( in that there is no proof that you ~must~ factor to break ; or what the complexityclass of factoring is )
asciilifeform: asciilifeform's cut of mpi did not include primegen or rsa.c
asciilifeform: it ain't in mpi
asciilifeform: and asciilifeform can read hexdump of x86 , mostly without hiccuping, and mircea_popescu prolly can read pdp11 oct dump, but yet for some reason folx pass around sources...
asciilifeform: much as i like sexpr, a sexpr dump of a vector drawing is not humanreadable either. at least not with my puny brain, i have nfi, perhaps mircea_popescu can render these in his head as he reads'em ?
asciilifeform: may as well represent as hexdump of jpeg.
asciilifeform: that's what linear array text is a cheap, impoverished hack approximation to.
asciilifeform: i'm almost surprised that mircea_popescu hasn't yet thought of , e.g., anathemizing ascii in favour of own, arbitrary arrangement of alphabet, strictly for incompatibility's sake; or to proclaim the 17-bit byte...
asciilifeform: at one point asciilifeform planned to cut out the allocator from mpi entirely, but ditched whole thing before ever getting there.
asciilifeform: elsewhere, asciilifeform contemplates , of what is made the black soot that one finds inside servers. wish i still had where to gc/ms...
asciilifeform: ( and i concede the point to mircea_popescu , boat prolly does not work for the contemplated use , in the general case )
asciilifeform: as mircea_popescu quickly figured out, asciilifeform's interest in boats is of a very peculiar kind, and not simply because he likes water.
asciilifeform: forget about matching, how about simply not burning the coin
asciilifeform: http://btcbase.org/log/2017-12-19#1754135 << emphasis was quite deliberate on 'this is orthogonal to the problem contemplated'. yes, it is solvable, there are several known obvious solutions.
asciilifeform: compared to, say, naive self-feedbacking inverter clock, or r-c clock.
asciilifeform: i have nuffin against mircea_popescu's beingimpressed.
asciilifeform: point is, scale alone dun impress, or we'd all eat, very impressedly, at mickey d
asciilifeform: rmoar impressive
asciilifeform: i can picture that it'd impress folx who experienced 'typical' technology being webolade, ducttape, perl. the way austrian bidet impressed asciilifeform's grandfather.
asciilifeform: pow where having found the prev champ is of ~any~ advantage, is ipso facto retarded tho.
asciilifeform: very rough attempt.
asciilifeform: and yes mircea_popescu this item is an attempt at the unified theory, rather than proposal for concrete cointron.
asciilifeform: i gave an example scalar, 'coins moved but over 1 block delta'. it is by no means the only possible.
asciilifeform: ( it was perhaps 80% of how asciilifeform cut koch-mpi , by similar proportion )