log☇︎
66100+ entries in 0.037s
mircea_popescu: "if i tell truth -- moron cousins back home laugh at me ; if i tell lie, they also come over -- i laugh at them."
a111: Logged on 2018-10-24 16:58 Mocky: no dude, they have fambly there who love it. they would love too!
mircea_popescu: http://btcbase.org/log/2018-10-24#1865590 << one time, a moron/filipina/african/whatever got $500 together, and in preference of buying indoor plumbing, or a gf/goat/whatever, bought miami ticket. once there, discovered it sucks terribly. first impulse was to leave a very scathingly honest review on miami.yelp ; but in the 18 minutes the page took to load (hurray for "modern" ux2.0 pid eins!) they changed their mind, left ver ☝︎
a111: Logged on 2018-10-24 16:57 Mocky: unrelatedly, the miami in these filipinas and africans is off the fucking charts. they literally cannot sniff even a whiff of 'america aint that great' without spitting out 'america is the best, how could you even think it's not'
mircea_popescu: http://btcbase.org/log/2018-10-24#1865587 << sad way to go through life ; but then again bulgarians thought "byzantine is best" way into 1200s. ☝︎
mircea_popescu: portability via vtree rather than ifdefs/wrappers/etc.
a111: Logged on 2018-10-24 16:03 asciilifeform: bvt: on contemplation, i'm thinking possibly mips should simply get own v-branch, if we ever actually get hold of a mips.
a111: Logged on 2018-10-24 14:15 asciilifeform: the .c absolutely gotta be bug-free tho, or it sinks yer whole proggy
mircea_popescu: http://btcbase.org/log/2018-10-24#1865550 << this sounds sad. ☝︎
a111: Logged on 2018-10-25 01:26 asciilifeform: previously , from last 2+yrs of reading docs, i laboured under the impression that the only process that demands secondary stack, is ~returning~ variably-lengthed objects. rather than simply passing'em forward as 'in' param. which in erry context OTHER than generic, worx .
diana_coman: http://btcbase.org/log/2018-10-25#1865729 -> ugh; I think I might have even seen this at some point before but I did not investigate it ☝︎
deedbot: http://bimbo.club/?p=65 << Bimbo.Club - TMSR Log Summary - 10/20/2018
a111: Logged on 2018-10-23 22:30 asciilifeform: defo seems to be a misconfigured/maliciously-configged shitfork noad, none of the tx hashes in the inv's line up with anything from human planet
mircea_popescu: re-doing this every few years seems eminently 'dammi tempu ca ti perciu'. ☟︎☟︎
mircea_popescu: asciilifeform so let them get to know you ; nothing wrong with derps hearing of the most serene republic.
asciilifeform: http://btcbase.org/log/2018-10-25#1865738 << 8192 , if can be fit, then can have 4096b rsa without 'bignum', lol ☝︎
asciilifeform: ( i omit to mention ~large~ fabs, given as if you aint representing a large and known $$$ concern, they dun even return calls )
asciilifeform: granted in past 2y since i last looked, the mythical beast of 'small fab' could have been born
asciilifeform: there's a coupla 'small scale' fabs, but on close examination smell like ripoff, they ship with literally 0 guarantee of yield , and in laughable qty , and with laughable transistor count, and -- to add insult to injury -- die packaging not included, you gotta somehow find someone to do it, somewhere ☟︎☟︎
asciilifeform: http://btcbase.org/log/2018-10-25#1865735 << i took a stab at this 2y ago, was very frustrating on acct of asic-baking not being a 'cash and carry' process like e.g. pcb-baking, but a heavily meat-powered affair where the derps want to 'get to know you' to figure out how much they can fleece ☝︎☟︎
asciilifeform: prolly not worth the bother, but in principle solid imho
a111: Logged on 2018-10-25 04:57 mircea_popescu: what, the supposed interloper can't hash is the idea ?
asciilifeform: http://btcbase.org/log/2018-10-25#1865742 << diddled cable, port, etc would not know the on-chip salt. ☝︎
a111: Logged on 2018-10-23 17:11 asciilifeform: ( nao i'm curious, what, by d00d's lights, is 'full node', and where might one get such a thing )
mircea_popescu: http://btcbase.org/log/2018-10-23#1865401 << this is perennial wank in the style of "not a true church" etc. xtian minds at work. ☝︎
mircea_popescu: what, the supposed interloper can't hash is the idea ? ☟︎
a111: Logged on 2018-10-23 15:57 asciilifeform: i'ma let mircea_popescu ponder whether this kind of thing is worth doing
a111: Logged on 2018-10-23 14:19 asciilifeform: i'ma describe , for the l0gz : ideal cpu for crypto would be something quite like the schoolbook mips.v -- no cache, no branch prediction, no pipeline, no dram controller (run off sram strictly), a set of large regs for multiply-shift , and dedicated pipe to FG (i.e. have single-instruction that fills a register with entropy )
a111: Logged on 2018-10-23 14:09 asciilifeform: if this were a bake-by-the-thousands product, we could bake asic. but currently this is not realistic imho
a111: Logged on 2018-10-23 13:44 asciilifeform: http://btcbase.org/log/2018-10-23#1865312 << ideally we oughta bake the new one, with ice40 & scintillator, imho
asciilifeform: ( how ran into this : sneak preview of mmap demo : http://p.bvulpes.com/pastes/VDYWv/?raw=true << path is set cleanly, as part of the generic invocation. but turns out this dun work (unless secondarystackism is enabled) , as somewhere internally it tries to ~return~ the string ☟︎
asciilifeform: previously , from last 2+yrs of reading docs, i laboured under the impression that the only process that demands secondary stack, is ~returning~ variably-lengthed objects. rather than simply passing'em forward as 'in' param. which in erry context OTHER than generic, worx . ☟︎
asciilifeform: meanwhile, in today's gnat retardations : apparently it is impossible to use ( but can define!!!11 just fine ! ) a generic that takes a String as 'in', without secondary stack.
BingoBoingo: asciilifeform: ty, fxd
asciilifeform: ideally you want device with ~no~ flash storage at all on the pcb, to avoid even theoretical possibility of retaining bits of key when unkeyed.
asciilifeform: ( pc-os/fw-based disk crypters are retarded, iirc subj was well covered in old thrds )
asciilifeform: the 1 non-negotiable aspect is that there must be 0 pc-side involvement in or awareness of the thing.
a111: Logged on 2016-12-24 01:46 asciilifeform: mircea_popescu: all schemes where the transform is of 'payload itself' and 0 entropy, suffer from immediate 'penguin problem', https://blog.filippo.io/content/images/2015/11/Tux_ecb.jpg .
asciilifeform: ( the problem of ciphering a block device in such a way as to avoid the penguin ( http://btcbase.org/log/2016-12-24#1590007 ) is tricky but not insurmountable ) ☝︎
asciilifeform: ( for the l0gz : from asciilifeform's pov, 'sane disk crypter' is an item that gets keyed via onboard keyboard jack, e.g. serpents, the attached disk, and unkeyed when powered off or at the closing of a contact attached to $whatever ) ☟︎
a111: Logged on 2015-09-22 03:01 asciilifeform: speaking of, last i checked, 'trezor' was still reflashable from the usb jack.
asciilifeform: ( usb controllers, on other hand, appear to -- without any known exception -- suffer from http://btcbase.org/log/2015-09-22#1282100 and related ) ☝︎
asciilifeform: iirc the colouring was originally of telephone cables, in ww2-era us army.
asciilifeform: ( 'red', for n00bz / folx far from usa culture -- refers to 'contains seekritz' )
a111: Logged on 2018-10-24 20:31 phf: i like to keep things red/black, so that e.g. red disk plates go into tomato soup at some point, but considering how leaky the whole system is, there's not really a red/black within the same machine anyway
asciilifeform: http://btcbase.org/log/2018-10-24#1865708 << if pc iron had its shit together, there would not even need to be such a thing as 'red' disk -- only (temporarily) 'red' sram, and buncha freely backed up 'black' disk. ☝︎
asciilifeform: BingoBoingo: s/fellow though/fellow thought
deedbot: http://qntra.net/2018/10/media-force-bomb-identity-on-to-harmless-packages-in-attempt-to-forment-hysteria/ << Qntra - Media Force "Bomb" Identity On To Harmless Packages In Attempt To Forment Hysteria
phf: i like to keep things red/black, so that e.g. red disk plates go into tomato soup at some point, but considering how leaky the whole system is, there's not really a red/black within the same machine anyway ☟︎
phf: i think it's an open question for the logs, whether or not /tmp is canonical place for putting temporary files, and whether or not writing a copy of what's being pressed in some arbitrary place (for all practical purposes) is a good idea ☟︎☟︎
phf: bvt: i think it's fine as is. scratch your own itch and all that
bvt: would you consider /tmp security issue resolved from vpatch's view if TMP/TMPDIR is respected?
a111: Logged on 2018-10-19 01:41 asciilifeform: zeptobars seems pretty dead; their site is up, but pretty sure that all of the pics therein, were there last yr
asciilifeform: phf: see if you can figure out wtf happened to zeptobars, also... ( http://btcbase.org/log/2018-10-19#1863863 ) ☝︎
bvt: hi, phf! i can provide a follow-up vpatch for respecting TMP/TMPDIR
phf: yeah, this time around i'll have plenty of time to investigate all the ru corp details, and also photos
BingoBoingo: Don't forget to pack the camera
phf: i'm preparing for an extensive jump to moscow, so i've not really had much time to speak
phf: old time reader, first time writer!
phf: i grok the reasoning, but there are two issues: as of right now nobody's mounting to nfs, but at least in my stack tmp is not always as secure as other places i might be pressing, and the patch doesn't respect the environment TMP/TMPDIR convention.
lobbesbot: phf: Sent 2 days, 2 hours, and 23 minutes ago: <asciilifeform> in bolix lulz : loox like dks relisted that 'ivory' for 3rd time nao... apparently not so many eager-worth-of-$5k archaeologists any moar
a111: Logged on 2018-10-23 21:41 bvt: a better write-up on the vpatch temporary file creation: http://bvt-trace.net/2018/10/vpatch-replacing-mktemp3
phf: http://btcbase.org/log/2018-10-23#1865503 << i threw your patch on btcbase, it looks good, though i'm not sure i agree with the decision to put temp file in /tmp. the point of putting it in same hierarchy as press, was to avoid the whole cross-file-system issue ☝︎☟︎
asciilifeform: really, anyffing that happened 1000+ blox ago, oughta be considered permanent, even if martians land.
asciilifeform: it's really a classic example, imho, of a mechanism that requires wot ( and ergo, an out-of-band forcing knob, 'no, you do not get to rewrite history, even if you have 9000 sybils' )
asciilifeform: and yes a node you plug in today ~will~ likely sync, but this is only because the noise floor is low enuff.
asciilifeform: i strongly suspect that the general case of 'establish the troo historic longest chain, strictly from the network, consisting of arbitrary portions of honest and dishonest nodes', without some variant of cement, is not solvable in general case
asciilifeform: the fact that this q gets asked at all, is proof that the network does not actually rise to the level of full automatism.
mod6: Ok, yeah. I still need to go back and re-read the ~last week of logs so I'm up to speed.
asciilifeform: consider the frequent lament 'my node is stuck'. how do you ~know~ that ~yours~ is stuck, and not the world.
asciilifeform: ( if were working strictly 'by the net rules', no one would ever do this, 'i have a node, it knows what the world height is', but this is not the actual practice )
asciilifeform: even the act of looking at the heights of other nodes, with naked eye, when syncing your own, is a primitive form of checkpointism.
a111: Logged on 2018-10-22 22:54 mircea_popescu: lots of things give this "make sure you have same blocks".
asciilifeform: ( and i'll add that 'i sync all my new noades from existing ones' is a form of checkpointing , yer still weaseling out of using 'strictly clean' http://btcbase.org/log/2018-10-22#1865227 mechanism , there ) ☝︎
asciilifeform: the only practical defense against this is checkpointing, afaik. ( the prb folx tried to defend with 'orphanage', but with finite ram this does not actually solve the problem in the general case, simply ensures that different noades will wedge at different times )
asciilifeform: mod6: in fact, and iirc i discussed this 2y or so ago in the l0g, by my current understanding of the reorg mechanism, it is possible to wedge ~any~ noad by throwing a specially- 'retro'-mined block with a higher work delta than the 'genuine' one at a particular point. then reorg dun trigger at all. ☟︎
a111: Logged on 2018-10-24 18:37 asciilifeform: current flagship trb cannot be replayed 'from genesis', but can be from 168000, per http://btcbase.org/patches/genesis#L3542 .
asciilifeform: http://btcbase.org/log/2018-10-24#1865668 >> err, from 168001, to be pedantic ☝︎
asciilifeform: mircea_popescu was not fond of 'cement', because sees (correctly) that it is a kludge. but imho given the single-threaded classical trb, it or something like it, is necessary
mod6: (if it doesn't take too much time to look into anyway, could be interesting data)
mod6: right, could be worth a test and perhaps the 'cement' suggestion.
asciilifeform: current flagship trb cannot be replayed 'from genesis', but can be from 168000, per http://btcbase.org/patches/genesis#L3542 . ☟︎
asciilifeform: theoretically it'll get reorg'd when honest noad later connects. but afaik this has not been tested, i personally do not know if a 1000+ -blocks reorg will succeed.
asciilifeform: speaking moar generally of replays -- because of the idjit method shitoshi used for block-gettin', where 1 peer can ~monopolize connection for just about as long as he wants -- a stock trb node , syncing from empty, is in fact in a position to be fed just about arbitrarily long replay chain. which is why my interest in sane checkpoint variant.
mod6: *nod* Ok. T'was interesting anyway. Cheers.
asciilifeform: mod6: i think there's also an ordinary (as they go) prb noad mixed into that pcap
asciilifeform: bvt: ty
asciilifeform: i can't picture against whom such 'replay' would possibly do anyffing, tho
asciilifeform: mod6: either that or '1 man band', mined'em all, and forgot to set his clock..
bvt: comment approved, i would do a writeup on this topic (so far ETA middle of next week, this sunday night very optimistically).
asciilifeform: the 1 puzzler is why the derp back-dated'em; if the related tardstalk piece is to be believed, the particular shitcoin did not exist in 2015
asciilifeform: mod6: the shitnoad sends ~same miniature blox , pretty much, again & again
mod6: So looks like idiot kept sending the same ones over and over.
mod6: That they were captured at different times. I dug through the pcap for the 'prev' hashes that were listed in the paste, all the ones that I spot checked were in there.
mod6: see that's what I thought.
asciilifeform: i dun have a tcpdump on that thing at all times, lol, no amt of disk count conceivably suffice
asciilifeform: though it is possible that some or all of'em were received again and ended up in there, later
asciilifeform: mod6: they were not. see log, i set up the tcpdump ~after~
mod6: asciilifeform: can you confirm that the bastard blocks that were listed here http://p.bvulpes.com/pastes/4GZTO/?raw=true were caputred at the same time as the pcap that you pasted?
BingoBoingo: The declaration that one isn't a pink manhooker isn't something the Uruguayos would say, but they understand it.