log☇︎
178900+ entries in 0.032s
asciilifeform: 4GB RAM, SSD drive, the works.
asciilifeform: achtung, panzers!
asciilifeform: BingoBoingo ^
asciilifeform: https://cryptome.org/2015/09/ulbricht-280-283.pdf << sr trial censored bits will stay censored.
asciilifeform: 'Chances are that your bank already forked C++ because they didn't like its open nature, and you now have to pay millions every year to the one guy who knows where all the libraries are.' << ahahahaha this is a thing of beauty
asciilifeform: 'We know that millions of transactions per second can be scary to some, especially banks who still call their customers and require them to fax in documents. In myBlockchain, you can limit the rate of transactions per second by requiring verification by a shamefully underpaid human being in your "back office" in the third world, just like you are used to.' << mega-win
asciilifeform: tr0l0l0l
asciilifeform: !up analmaster
asciilifeform: analmaster: and you, for some reason, are rowing the galley today ?
asciilifeform: analmaster: a bit. about to do moar.
asciilifeform: !up analmaster
asciilifeform: i recall there was a thread where mircea_popescu unzipped and pissed on standards, but they are pretty much the only way you get to have (2) and (3)
asciilifeform: (a frag is not a useless thing, has its place where nothing else will do. but only there.)
asciilifeform: i'd include forth, but it has the 'safety' of a frag grenade.
asciilifeform: *them
asciilifeform: if your book didn't come with then, get yer money back
asciilifeform: whips and cuffs come with ada
asciilifeform: (or it is not properly speaking 'native')
asciilifeform: under (3) i also include that native compiler must support unix threading
asciilifeform: that's pretty much it.
asciilifeform: under (1) i also include bounds checking and sane error handling
asciilifeform: 1) type safety 2) MULTIPLE independent implementations 3) at least two NATIVE compilers exist 4) written international standard, preferably published on dead tree
asciilifeform: rough and non-exhaustive summary of what 'for adults' means:
asciilifeform has been recently carrying out a kind of survey of programming systems ~built for adults~. so far, nominees: common lisp, ada, standard ml. and that's ~it~
asciilifeform: http://log.bitcoin-assets.com/?date=20-09-2015#1280374 << recall how everything is 'oversold' in the cable modem sense ? where actually ~using~ all of what you paid for, will break it or use it up in record time? well, this. ☝︎
asciilifeform: mod6: my box is not wedged.
asciilifeform: mod6: same
asciilifeform: noez, he wanted genuine dead souls, not synthetic dead souls !!111111 ☟︎
asciilifeform: 'Recently, however, Brar has fallen out of love with Facebook. He discovered — as Business Insider reported recently — that his Facebook fanbase was becoming polluted with thousands of fake likes from bogus accounts. He can no longer tell the difference between his real fans and the fake ones. Many appear fake because the users have so few friends, are based in developing countries, or have generic profile pictures.' << oh
asciilifeform: he wrote some code which could, theoretically, be used to make this.
asciilifeform: this very thing.
asciilifeform: (yes, someone did half of it, a btc's worth, but the result is not yet something i can send off to the print house and get a wall poster) ☟︎
asciilifeform: esp. since nobody ever did the chore, yet, of making a usable wall-sized call graph like i asked for
asciilifeform: it doesn't hurt to have it. for the call graphs.
asciilifeform: (emacs will tell me where a string occurs, sure, but this is pointedly NOT what i want)
asciilifeform: editor doesn't give concordance
asciilifeform: i prolly ought to set the thing up on local disk
asciilifeform: but seeing rel1 in it gets old, fast.
asciilifeform: i use it every time i look at the thing at all.
asciilifeform: mod6: the lxr thing is indispensible
asciilifeform: laterz.
asciilifeform: http://btc.yt/lxr/satoshi/source/src/script.cpp#1188 << verifying a tx sig
asciilifeform: l0l
asciilifeform: http://btc.yt/lxr/satoshi/source/src/main.cpp#0941 << we start verifying block
asciilifeform: mircea_popescu:
asciilifeform: hence i am stuck using jurov's original. here goes.
asciilifeform: other than for the flow graphs.
asciilifeform: the thing is graphically spiffy but entirely worthless in practice.
asciilifeform: and the file browser, always visible, is mega-annoying
asciilifeform: doxygen is RETARDED, it takes actual sweat to so much as link to a specific line of src
asciilifeform: ;;later tell mod6 'lxr' is 1001 times more useful than doxygen. can haz both plz ?
asciilifeform: this is btw a beautiful pun, often exploited, in ru: язык ада == 'the language of hell'
asciilifeform: they will program in ada, in hell
asciilifeform: i have the thing on screen as we speak.
asciilifeform: it is.
asciilifeform: let's actually do this one
asciilifeform: and freed after each script ver.
asciilifeform: the scratch space used for the verification is allocated on the stack ☟︎
asciilifeform: tx-en are verified serially.
asciilifeform: mircea_popescu: i am curious as to the logic of this inference.
asciilifeform: this is called fragging.
asciilifeform: (either that, or tell me where the buries treazurez are!)
asciilifeform: perhaps mircea_popescu ought to get busy teaching his pets cpp
asciilifeform: unless i somehow stumble across buried treasure, etc., it will have to be nailed by someone who is not me.
asciilifeform: i must also remind people that, sadly, these days i do not have anything close to the amount of time and energy needed to properly nail this thing.
asciilifeform: punkman: what i ended up doing was manually combing the code for 'what gets eaten but never shat', and found the block index to be the obvious culprit.
asciilifeform: punkman: later i created a mechanism to measure only consumption from within the process proper, but i did not have time to turn this into a plot.
asciilifeform: punkman: it appears to come from liberated ram no longer needed for disk cache
asciilifeform: useless, garbage number, anyone who claims to have a calculated value for it is lying or utterly illiterate
asciilifeform: btw there are misleading figures circulating re: 'size of the mempool today is 5MB' etc.
asciilifeform: for all the good it did, re: pogo...
asciilifeform: at one time there was a '3' - glibc-free, static, rom-burnable bitcoind. but we have it now.
asciilifeform: i put an obscene and prolly unjustifiable amount of sweat into narrowing down the causes of the misery to 1 and 2.
asciilifeform: JUST FOR THE MOTHERFUCKING BLKINDEX
asciilifeform: (and then some)
asciilifeform: we can't have the thing occupying the entirety of ram.
asciilifeform: ('2' shows the behaviour of a deterministically-syncing (from disk: http://therealbitcoin.org/ml/btc-dev/2015-July/000107.html -- (!!!) node. the block index grows linearly, ~300 byte per block.) this is entirely undigestible on a pogo.
asciilifeform: 2) http://therealbitcoin.org/ml/btc-dev/attachments/20150701/rss_d1746f76523316edcdc82326213f8953bf6f0d09.png
asciilifeform: 1) hard-limited, value-weighted tx mempool
asciilifeform: pogo is pending on two undone things:
asciilifeform: http://log.bitcoin-assets.com//?date=11-08-2015#1234821 ☝︎
asciilifeform: rewinding to, ☟︎
asciilifeform: (phoundation's header-first-sync thing is not a node...!)
asciilifeform: realize that nobody but us (and the quasi-mythical 'smart miners') are running full nodes now.
asciilifeform: (and so simply ends up wasting time spent on reconnecting)
asciilifeform: and when it does, ends up selecting a new peer more or less wildly
asciilifeform: mircea_popescu: the most dire flaw, per my current understanding, is that the thing is loathe to discard a peer ☟︎
asciilifeform: how else.
asciilifeform: naturally
asciilifeform: mircea_popescu: any blackholing observed ?
asciilifeform: yes, nominally the thing is a p2p gadget, this oughta work, no? but in reality, yer cooking with gutter oil
asciilifeform: ahahahahaha
asciilifeform: mircea_popescu: who are you pulling from ?
asciilifeform: hm does gribble have a block-->epochaltime function ?
asciilifeform realized that this question is auto-answerable
asciilifeform: how long have you sat there ?
asciilifeform: 375290 and running
asciilifeform: mircea_popescu: nein
asciilifeform: TomServo: for all we know, it just split into parcels
asciilifeform: i can picture it.