log☇︎
122000+ entries in 0.066s
trinque throws that on the TODOs
trinque: what a terrible error message. ☟︎
asciilifeform: ( and what was the generating node's ? )
asciilifeform: and, importantly -- what is the node's height ?
asciilifeform: is tx of unusual size ?
asciilifeform: or was this a process flow that worked 9000 times before, and otherwise virginal
trinque: nope, tx bin hex slurped from qr code
asciilifeform: right, but is there any diff b/w how trinque fed it to 'other tool' and how he fed to this one
trinque: other tools say it's a normal tx, and see the input
asciilifeform: ( is it possible that it got cut or mutilated ? )
asciilifeform: i gotta ask : how didja generate the txturd
trinque: I don't see that he does anything to transaction parsing there
trinque: pressed to makefiles then patched polarbeard atop manually
asciilifeform: and http://btcbase.org/patches/polarbeard_add_sendrawtransaction_rpc is the press point ?
asciilifeform: trinque: plox to describe the experimental setup ( not pedantism for the sake of pedantism, this, it's important )
trinque: though I don't see how he'd have borked tx parsing
trinque: totally possible it's in the polarbearded portion. I'm digging
asciilifeform: trinque: which trb is this
trinque: hm, I have a transaction for which trb considers the CTransaction "vin" vector to be empty, but which clearly has an input.
asciilifeform: so potentially findable there, if only anybody remembered the actual phrasing
asciilifeform: in other finds, unlike google, yandex indexes ~all of trilema
mircea_popescu: nah, that's just a reference to an old romulus vulpescu translation of decameron
asciilifeform: ( i dun have a greppable trilema here, so can't immediately say where )
asciilifeform: it was in a trilema article
mircea_popescu: hmm, where the hell is the place where i say the father's responsibility to his daughter is to shove a pound of raw prime beef down her throat every day and naught else ? ☟︎
a111: Logged on 2015-08-11 03:24 asciilifeform: 'ONE way of feeling infallible is not to keep a diary. Looking back through the diary I kept in 1940 and 1941 I find that I was usually wrong when it was possible to be wrong. Yet I was not so wrong as the Military Experts. Experts of various schools were telling us in 1939 that the Maginot Line was impregnable, and that the Russo-German Pact had put an end to Hitler’s eastwards expansion; in early 1940 they were telling us
mircea_popescu: http://btcbase.org/log/2015-08-11#1234154 << this is such an epic tidbit btw... ☝︎
mircea_popescu: (steam engine existed because metalworking, and the metalworking involved exists because cannons. industrial revolution is the result of having stolen gunpowder.)
mircea_popescu: twas the arabs, they got 0 from india and it sparked.
asciilifeform: but the point stands.
asciilifeform: fwiw the deep historicalcrackpots seem to think it wasn't even arabs, but the now-vanished aryans or whoever.
asciilifeform: the sad part re inventing things.
mircea_popescu: and somehow THEY'RE supposed to be the uncivilised orcs.
mircea_popescu: poor arabs, they invented all this shit, we ran with it with our inept ways and nearly fucked it into the ground
asciilifeform: if we wrote like arabs, there've been no controversy, i bet
mircea_popescu: this is back to the glyphs discussion all over again. "fix your printer!"
mircea_popescu: the other one does ~this same thing~ but ~to the machine~.
asciilifeform: try likewise with 'long' instead of 'int', to see effect on 64bit parcel
asciilifeform: try this on littleendian and bigendian box.
asciilifeform: gcc -o endian thisitem.c
mircea_popescu: show me this ?
asciilifeform: whether this matters, is obviously arbitrary q.
asciilifeform: mircea_popescu: re the 'guillotine neck vs mandible', if it ain't obvious, i'll spell it out ftr : bigendian nums look 'ffaistic' when hexdumped, i.e. correct . littleendian -- you gotta mentally flip'em. ☟︎
asciilifeform: btw arm and mips have toggles for endianism
mircea_popescu: how i regret it! every day i mourn it! they wounded me so very deeply, these idiots, with their idiotic misbehaviour! to the very core of my being i suffer for their failure to have ammounted to a hill of beans!
a111: Logged on 2018-01-25 02:09 mircea_popescu: this is like saying guillotining the neck rather than the mandible or the shoulderblades is completely arbitrary.
asciilifeform: mircea_popescu: and most of the knob params are of the http://btcbase.org/log/2018-01-25#1775939 kind. ☝︎
mircea_popescu: such a disadvantage this puts me at, seriously!
mircea_popescu: awww. so that means i can say whatever and nobody has any ground to stand on and argue "his" way ?
asciilifeform: mircea_popescu: i hatetobreakittoya, but WHOLE FUCKING pseudoengineering kompyooting thing, is 'whisperproduct'
mircea_popescu: because afaik this is a whisperer's product and it THEREFORE carries no weight.
mircea_popescu: show me where this cost analysis is published.
mircea_popescu: if there were a costless thing, by all means. but "between saving for six months to afford the thing i need and "buying" this other thing i don't need on easy rates i choose the former" though ?!
mircea_popescu: i do noit dispute it does cost, but so does this other isnanity.
mircea_popescu: on every add. what, the cost of the shift is the issue here ?
mircea_popescu: asciilifeform do it shift two and carry the last bit adequately ?
mod6: hanbot: http://p.bvulpes.com/pastes/t0piX/?raw=true << looks that way -- however, keep in mind the entire press did not finish, so hard to say that there couln't have been more if something else wouldn't have puked from hunks or whatever.
asciilifeform: ( it ain't impossible. but i can't immediately think of an economical method )
asciilifeform: mircea_popescu: i'd like to see your algo for 2s-complement add/sub for a hypothetical box where sign bit is not the senior bit
mircea_popescu: the whole edifice is rotten. special order ? if they wanted this SHOULD HAVE CHANGED THE SIGN BIT POSITION OMFG
mod6: hanbot: ok. let me take a look here...
hanbot: mod6 there should be one orig, is in the mp-wp i was handed
asciilifeform: i'll confess , i'm with mircea_popescu on this one, how much time is spent printing and testing sign bits ?
mircea_popescu: asciilifeform i don't understand the argument. so you write left to right, so what does this say ?
mod6: crap, ignore that'
mod6: ben_vulpes: yes, i found this one in the genesis: +(function(A){A.widget("ui.draggable",A.extend({},A.ui.mouse,{init:function(){var B=t
asciilifeform: mircea_popescu: the 'philosophically consistent' ( hey kurchatov! ) method is: little-endianism . but with it, you're stuck loading a whole parcel to test its sign bit ( i dun give a fuck, personally , on modern iron ) but -- unless yer an arab -- flipping words prior to printing , in the civilized style, left to right
mircea_popescu: because it rotates this way it is therefore not a valid encoding and case closed.
mircea_popescu: big endianism is the proposition of taking a pile of bits, and sorting them such that they representing larger powers of two are later than those representing smaller powers of two ; but only for chunks of bits of an arbitrary lengths ; chunks longer are ordered in ~the contrary fashion~, so ab is to be ordered as ba by this scheme, but abcd is to be ordered as badc.
hanbot: mod6 thanks very much for looking --that error was 2nd headscratcher for me. phf's vdiff.sh was used to make this, fwiw
mod6: what's weird is that it actually output that in the pressed file.
ben_vulpes: mod6: magic strings in the b64!
mircea_popescu: to make the full argument here in plain text :
mod6: hanbot: http://p.bvulpes.com/pastes/HrKA1/?raw=true << Here is what I know, for now. There are some comments at the bottom.
asciilifeform: possibly worth reviewing why people even came up with bigendianism. it was partly from 'can test sign bit by looking at zeroth byte' , and partly the ben_vulpes ( from #trilema-mod6 log linked 2d ago ) problem -- 'let's store words in the order in which they get printed'
asciilifeform was waiting for this
mircea_popescu: we could actually declare big endian notation to be WRONG, on the grounds it's inconsistent.
asciilifeform: ( attach a dynamo to dijkstra's corpse prior to testing, yes 'oughta tell From First Principles!111' )
asciilifeform: btw iirc trinque has a bigendian machine with a working gnat.
diana_coman will read; and then re-read
asciilifeform: ( i recommend to diana_coman and even to mircea_popescu to read the linked doc )
asciilifeform: and the effect is what is desired, namely the layout is exactly the same, independent of whether the code is compiled on a big-endian or little-endian machine. '
mircea_popescu: i wouldn't go so far as have to, but it is a fact it'd help me in this point.
diana_coman: mircea_popescu, ugh, I'll have to put in those link for selection, won't I
mircea_popescu: diana_coman i would right now like to, for a great piece i'm writing, link to "The choice of Ada as programming language for this implementation" specifically out of all http://www.dianacoman.com/2018/01/25/eucrypt-chapter-7-keccak-sponge/ because that's the sort of fine tuned context linkage i use. wut do ?
asciilifeform: ( other than to bake own iron with 1bit busses etc )
asciilifeform: i described the two known pills ( without endorsing a particular one ) against endianism. afaik there is not a third.
mircea_popescu: well in any case, there's a week to sort this mess out.
asciilifeform: diana_coman: the short version is that the cpu is a physical object. this is an eternal and incurable headache for programmerz, yes
mircea_popescu: o hey, i hadn't noticed that they DIDNT LIQUIFY
asciilifeform: and yes the Bit_Order thing works, all kinds stuff would immediately liquify if it didn't
diana_coman: trouble is ...why is it worth having this headache to start with
asciilifeform: but i think mircea_popescu gets it
mircea_popescu: o good grief. must i include all the 0s ?
mircea_popescu: otherwise you could just check to see if 0F is smaller or larger than F0 obviously
asciilifeform: ( and if it didn't -- it ain't hard to determine it mechanically . i will leave it as exercise how )
diana_coman: but "In this section we will review the effect of the Bit_Order attribute definition clause on byte ordering. Briefly, it has no effect at all, but a detailed example will be helpful" this is gold
diana_coman: this is why I said earlier "check endianism at runtime" because yes, in ada you can get that
asciilifeform: ( tldr : ada tells you the endianism of the box you're on )
mircea_popescu: "here's the source ; check to see it is correct ; and here's how your builder will fuck it up for you by replacing constants"