29900+ entries in 0.601s
mircea_popescu: ben_vulpes that's ok, it's because upwards mobility, see? you can now touch ceilings your parents couldn'
t.
pete_dushenski: podesta et al. might even have what it ~took~ to run the world of their formative years, but meanwhile time marched on and they've now wandered far, far from home. similarly, god help the lot of us in 30-40 years. don'
t forget just how old these team clitler fogies are either.
mircea_popescu: at least they won'
t be helping anyone with javascript.
adlai thinks mircea_popescu wants him to shut up! so if i don'
t !!up myself again -- good afternoon, good evening, and goodnight.
adlai: superstition ain'
t the way (tm) s (r)
mircea_popescu: asciilifeform that you don'
t know is exactly the point, now isn'
t it. not so dumb after all.
mircea_popescu: also the reason noobs can'
t write literature is because they imagine description needs to be exhaustive. so their prose turns tedious and then unreadable.
mircea_popescu: asciilifeform no, it doesn'
t choose. it HAPPENS upon a variant.
adlai: 'standard' obviously doesn'
t cover many cases, which is why it exists as a standard which can be referenced against.
adlai: dude was dangerous, he'd already been visited by cops in the past! (for, uh... growing too much grass, and i don'
t mean the happy kind)
BingoBoingo: <ben_vulpes> i didn'
t realize malt liquor was that fungible << It is!
ben_vulpes: i didn'
t realize malt liquor was that fungible
adlai: meh, btcfiat is such a saturated market anyways. there's probably free energy to minimize these days, but i couldn'
t have known that a month ago
adlai: asciilifeform: i refuse to get into "clhs doesn'
t actually say you're not allowed to give it an atom" territory
adlai: asciilifeform: in other wtf, isn'
t ., isomorphic to ,@!?
mircea_popescu: i didn'
t bring up the fucking apocalypse to fix some tabs.
mircea_popescu: i don'
t want fucking "codepoints" in my life. take your /x855 and shove it, bejaysus.
mircea_popescu: "we don'
t use in band but we have not well formed diffs which you can'
t tell"
ben_vulpes: i was hit with the ugly stick at birth, you can'
t scare me
adlai has translated php precisely once in his life, and ain'
t nobody good time to incf!
adlai: now that's a hearoglyph i haven'
t seen in a long time!
pete_dushenski didn'
t realise how much eur had weakened relative to usd until bb pointed it out. 1.05 yo!
pete_dushenski: the worst part of medium is that the images don'
t archive. this wouldn'
t be an issue for most republican blogs seeing as they're entirely text, but it's actually quite the bug for fiat writers, taleb included
mircea_popescu: nah, that's what my thing above : because of the state machine, you can'
t actually tell bit impact.
mircea_popescu: still, it is ~only way to get hash that doesn'
t do the things we don'
t like.
a111: Logged on 2014-10-08 19:19 mircea_popescu: einstein never got the damned formula out because luce irigaray didn'
t see why he'd privilege the speed of light over other speeds that are so much more important to us. and so on.
BingoBoingo: But yeah, didn'
t consider the construct before replying
a111: Logged on 2017-01-04 10:33 davout: i don'
t really see asciilifeform's issue with large 'formatting' patches, as long as it can be mechanically established that the changes a patch brings do not change any of the code semantics there should be no problem with arbitrarily large patches
a111: Logged on 2016-12-23 02:45 asciilifeform: (if a111 doesn'
t answer in $time)
davout: i don'
t really see asciilifeform's issue with large 'formatting' patches, as long as it can be mechanically established that the changes a patch brings do not change any of the code semantics there should be no problem with arbitrarily large patches
☟︎ davout: ah i didn'
t notice the two lines merged as one being seen as a move
ben_vulpes: also the preserved section goes from one line to two, and the diff-o-tron isn'
t saying anything about the leading paren on that bottom line
ben_vulpes: davout: i think the highlighting is trying to tell me that it thinks that `format
t "~{~A~}"' persisted from the previous commit to this one
ben_vulpes: i don'
t even programming and don'
t do that
mircea_popescu: also is the first stone of "well your computer doesn'
t actuallty work, does it" most normies may encounter.
a111: Logged on 2017-01-03 22:35 asciilifeform: ben_vulpes: my current (wholly nonexpert) understanding is that airplane DELIBERATELY omits 'hard interlocks' wherever possible, on the principle that not-being-able-to-X-when-you-must is worse than can-X-when-you-mustn'
t mod6: yeah, actually, now that I think about it, i was told that in this particular case I was talking about, the guy didn'
t even put in regular unleaded (87 octane), he put in like 110 octane racing fuel.
mircea_popescu: and in other news, girl preparing to weigh self, "if it shows me over what i started at ima jump out the window". me, equanimous "wouldn'
t it be better to jump out window if surprisingly light, than if surprisingly heavy ?'
mircea_popescu: so then use that. as the spec says, m.
t specifically left unspecified.
mircea_popescu: and no, not wholly mempool less. there is m.
t. what it contains - we care not. when problems will arise, they will be solved without impacting on the core scheme.
mircea_popescu: i don'
t think today's logic does anything ; and i don'
t expect carrying it forward is useful. spec does include room for trb.n to do some banning, including on the basis of passively exfiltrated data from trb.b. that a protocol for this purpose may later develop i don'
t dispute, but it's not included both because it's not needed and because it can'
t become a "dependency". it's not.
davout: but obviously retracting gear isn'
t a good idea
davout: asciilifeform: i don'
t thing the argument that the block validation logic can be found in the block validation logic is tenuous
ben_vulpes: haven'
t made checkpoints configurable, so solipsist nodes won'
t even mine
☟︎ mircea_popescu: still, the "frozen trb because networking" or "because badlt done block check" etc can'
t go on forever.
lobbes: That was a great read, thank you. Lined up exactly with my own anecdotal experiences. If I learned one thing in 'business school', it was how to properly bullshit. Only cost some 20k! Real learning didn'
t happen until after graduating (funnily enough, I also learned to drive -after- getting my license)
mircea_popescu: lobbes this incidentally explaisn why wikipedia is such shit - it's ~only function is a sort of open-sourced cliffnotes, and people would much prefer it to be bland and stupidly written so the teacher in class doesn'
t feel too inclined to think the kids' lifted material isn'
t his. after all he added all the flavour words in there!
mircea_popescu: it seems certain B.B belongs on disk. it seems likely B.
T also belongs on disk. it seems certain M.
T belongs in memory. it seems likely N.B also belongs in memory.
mircea_popescu: but it is not required for B.
T to be used only in this way or for this purpose. in principle there could be a whole pile of these, readily extended into whatever operator wants to do.
mircea_popescu: this scheme among other things cheaply allows the "add arbitrary new address to wallet", just have utility that (separately) processes B.B and produces new set of B.
T.
☟︎ mircea_popescu: in any case : TRB.N needs write access to N.B and M.
T and read access to B.B ; TRB.B needs read access to N.B and write access to B.B and B.
T. it may be a good idea to also give TRB.N read access to B.
T but this should be operator-knob
mircea_popescu: M.
T deliberately left unspecified, it is the equivalent of today's "mempool". perhaps should also be a ring buffer like the other 3.
mircea_popescu: otherwise it is discarded. B.
T may be pruned (according to arbitrary address list, for instance). Rate limiting in TRB.N may be constructed to observe N.B items that fail to propagate to B.B and ban the originating peers.
☟︎ mircea_popescu: TRB to be split into two parts : TRB.B and TRB.N. Queues B.B B.
T N.B to be created. TRB.N inherits the code to connect to peers. TRB.N reads blocks from peers, and puts them in N.B. TRB.N reads txn from peers and puts them in M.
T. TRB.N does nothing else (with the possible exception of rate limiting for peers). TRB.B reads N.B and verifies the blocks. if the block is verified it is added to B.B and its component txn to B.
T ;
mircea_popescu: yes, they're both "transactions" in the terms of the eventual datastruct they'll occupy. they aren'
t for that reason the same thing.
a111: Logged on 2017-01-03 19:59 asciilifeform: trinque: it isn'
t , currently, clear to me that you can make this cut cleanly without hard-breaking with the traditional protocol.
trinque: "don'
t talk to idiots" is a far broader problem than bitcoin