log☇︎
161800+ entries in 0.042s
mircea_popescu: but is also finite.
mircea_popescu: sure.
mircea_popescu: this will be done eventually, as the article says. but not without its costs.
mircea_popescu: the ~only way to do this in silicone is to make blocksized banks and line them up.
mircea_popescu: moreover, you still need all the accesses.
mircea_popescu: 1tb of ram will be overwhelmed by 20mb blocks in a few years.
mircea_popescu: this is an oversight. they want a change, fine, but they must fully commit to it.
mircea_popescu: ascii_butugychag different incentives. as it is now, changing the size doesn't automatically brick all miners.
mircea_popescu: but on the basis of what we currently known, a strict coupling there (4 or less bits of shift) is untractable
mircea_popescu: obviously there's no insurance against future technology.
mircea_popescu: aha.
mircea_popescu: so whatever new value we agree upon, it's fixed.
mircea_popescu: but that also means block size gets BAKED IN SILICONE
mircea_popescu: yes there's some economy of scale to be had with well designed flash banks, made each the size of a block etc.
mircea_popescu: the only reason asics exist is because sha256 you can do by hand on paper.
mircea_popescu: if you have a drive that seeks and also updates, why not have a cpu ?
mircea_popescu: can that drive seek 300k specific bytes on demand ?
mircea_popescu: ascii_butugychag is asic going to store the whole chain ?
mircea_popescu: CAREFULLY.
mircea_popescu: you gotta read carefully.
mircea_popescu: ascii_butugychag it's my recollection you can apply it on an endless pile of data, neh ?
mircea_popescu: "FOR SIIIIGNLET!!!!"
mircea_popescu: hehehe. thanks god we are better than that stupid shit.
mircea_popescu: anyway, yes, i'm taking the time from my days of orgies and icecream to read this thing.
mircea_popescu: well the v is well designed to be forgiving and helpful.
mircea_popescu: understand : you can't prevent people from working nor should you try.
mircea_popescu: ascii_butugychag yeah well.
mircea_popescu: polarbeard aha.
mircea_popescu: nevertheless : the grime's still there, and bitcoin would do a lot better with a better logging system
mircea_popescu: this has on one side exposed a lot of the underlying grime, and on the other side is bugging your centralist mind because you don't want to read thousands of lines of patchwork.
mircea_popescu: ascii_butugychag lemme summarize this for you. bitcoin eminently keeps shitty logs. a new guy came in and undertood the monstrous task of trying to fix that.
mircea_popescu: polarbeard i dunno that it was expected to either. prolly isn't, really. just, bitcoin code is too layered, random and messy.
mircea_popescu: i do object to return ret; in principle.
mircea_popescu: ascii_butugychag i didn't object to it in principle, but it's also not covered by the new logging model.
mircea_popescu: they ran out of reddit or something ?
mircea_popescu: !down Tasoshi
mircea_popescu: and my god, the return ret; stuff already
mircea_popescu: not to mention assorted garbage like throw runtime_error()
mircea_popescu: polarbeard mno, this is no good, it doesn;t solve the naked return problem. for instance (all from bitcoinrpc.cpp) : return error; at line 44 ; return "bitcoin server stopping"; line 162 sorta thing.
mircea_popescu: lmao what!
mircea_popescu: Tasoshi looky, im sure you have nice intentions et all, but intentions don't matter. put some actual sweat into it. answer the original question, answer it well rather than flailing around.
mircea_popescu: and flags would be nice
mircea_popescu: it doesn't say WHO was banned
mircea_popescu: for instance.
mircea_popescu: - return error("BANNED peer issuing unknown inv type.");
mircea_popescu: there's no way around this. what would you do ?
mircea_popescu: dude the fucking returns have to be fixed.
mircea_popescu: full disk is best disk!
mircea_popescu: polarbeard incidentally, did you leave any nude returns ?
mircea_popescu: ascii_butugychag yes but now necessarily monstruous
mircea_popescu: (miners currently use this incidentally, to some degree)
mircea_popescu: won't be too easy tho, asic needs EVEN MORE ram that way.
mircea_popescu: punkman quite, yes. this is deliberate.
mircea_popescu: what fucking vision.
mircea_popescu: fine, if you must. "meanwhile i read the code".
mircea_popescu: can you be specific ?
mircea_popescu: + printf(SERR SBLK "can't create database file %s\n", strFileRes.c_str());
mircea_popescu: oh.
mircea_popescu: phf http://www.intodns.com/btcbase.org and btw, did i say how much i like the blue and red and shit ?
mircea_popescu: !up ascii_butugychag
mircea_popescu: polarbeard http://104.131.72.249/patches/polarbeard_better_log_messages#selection-8295.32-8295.60 < plox no ' in loglines so people don't have to escape the shit out of parsing.
mircea_popescu: which is why i'm doing it.
mircea_popescu: no it's right as it is.
mircea_popescu: !up Tasoshi
mircea_popescu: polarbeard aite. ima slog through this, mind you that it's 2k lines will take hours.
mircea_popescu: BingoBoingo aha!
mircea_popescu: you can now tell all your sm friends lol.
mircea_popescu: anyone recall that 2012 brand of lolz ?
mircea_popescu: seems like they hired solidcoin to do their strategy.
mircea_popescu: anyway, as a general comment : next time start the whole process by designing this. it's a great spot to start!
mircea_popescu: i c!
mircea_popescu: waht is "SINF" by this logic ?
mircea_popescu: and these are prefixed by I W or A for info warn or alert ?
mircea_popescu: polarbeard i see.
mircea_popescu: phf set up an A record, should do the trick, hopefully.
mircea_popescu: now lemme see how the fuck i get this ns'd.
mircea_popescu: phf how about btcbase.org ?
mircea_popescu: well at this level yes, but we'll see more once i actually go throuygh the list, rulebook in hand.
mircea_popescu: it's an important point, must be documented well.
mircea_popescu: what's your rulebook to know what message goes in which flag ?
mircea_popescu: yes but which flags are used for which kind of messages, how we select the kinds, that sorta thing
mircea_popescu: well we're not there yet, so far just asking how you designed it / how you selected the list etc.
mircea_popescu: and they are MY logs.
mircea_popescu: because if i want to search my logs ima have to use your flags.
mircea_popescu: i dunno if you see this, but the way the flags are set impacts many people downstream.
mircea_popescu: you have a ns ?
mircea_popescu: phf lemme see what i have.
mircea_popescu: any idea what these are ? how they were selected ? etc ?
mircea_popescu: +#define SMIN "MIN "
mircea_popescu: +#define SWAL "WAL "
mircea_popescu: +#define SNET "NET "
mircea_popescu: +#define SBLK "BLK "
mircea_popescu: +#define SADR "ADR "
mircea_popescu: +#define SMEM "MEM "
mircea_popescu: +#define SPRC "PRC "
mircea_popescu: +
mircea_popescu: +#define SINF "INF "
mircea_popescu: +#define SWAR "WAR "
mircea_popescu: +#define SERR "ERR "
mircea_popescu: sooo...