Results 1 ... 250 found in all logged channels for 'f:asc http://therealbitcoin.org/ml/' |

(asciilifeform) asciilifeform: ( ordinary ssh tunnel illustrated in e.g. but dunno if solves for phf )
(asciilifeform) asciilifeform: whaack: see the various 'blackhole' posts by asciilifeform on ml. pretty straightforward imho.
(asciilifeform) asciilifeform: note, btw, that in the earlier linked ml experiment, asciilifeform demonstrated that most of block verification cost is in the idjit slowmo db
(asciilifeform) asciilifeform: ( there is no support for cement yet, this is only a corrected and sped-up variant of my orig. 'makesnap' from '18. )
(asciilifeform) asciilifeform: asciilifeform's cement maker. note, is buggy, i.e. needs whaack's 'dumpblock' patch to actually produce correct output, as it happens
(asciilifeform) asciilifeform: gotta move the old material ( the ml most importantly ) and emplace recent patches
(asciilifeform) asciilifeform: cgra: my 'makesnap' patch did this, but it needs this fix to work properly
(asciilifeform) asciilifeform: raw_avocado: http://therealbitcoin.org is the traditional place. for older stuff, in particular, the ml. errything else -- in the logs.
(asciilifeform) asciilifeform: whaack: no reason to hurry, lol, this bug sat for 6+y!!!! and no one, apparently, gave a shit until nao.
(asciilifeform) asciilifeform: gregorynyssa: i wrote the original vtron; and still use phf's updated (for keccakism) version of it
(therealbitcoin) asciilifeform: kiwi_46shake: at any rate, in case wasn't clear, whether or not 'bitcoin.foundation' owner is sending spam (or was hacked), is entirely unrelated, earlier org. the group this chan is about, opened in oct. of '14 , and concerned strictly w/ maintenance of the orig. client program. no one in the former participated in the latter, or vice-versa.
(therealbitcoin) asciilifeform: cgra: i wrote in '18 a patch to enable ~generating~ 'cement' . but not the receiving end.
(asciilifeform) asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-25#1020435 << thus far the only potential pill i've come up with is 'cement'. (i.e. noad eats a wot-signed list of block hashes, to then use during sync.)
(asciilifeform) asciilifeform: Aerthean: actually this gentoo still based on traditional glibc. static linking in it still has to be done by building a separate gcc + toolchain, or using ave1's gnat , or similar.
(asciilifeform) asciilifeform: shinohai: even objdump worx (as described in my original 'rotor' recipe)
(asciilifeform) asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-07-26#1017239 << there's ~6 years of history here ( and that's simply from asciilifeform's pov, other folx struggled longer. ) in '15, found that glibc project has been operated by wreckers, for years. and deliberately sneaks dyn. loads into 'static' builds. after some work, found cure -- to throw glibc the fuck out.
(asciilifeform) asciilifeform: whaack: at 1 time, asciilifeform wrote a mechanism, 'wires', to make it simple to create 'private' cliques of noads that can connect to one another. but abandoned from lack of in-wot interest. (didn't help that the 1st version was buggy, either)
(asciilifeform) asciilifeform: re pxeboot -- iirc in '15 i posted instructions re tftp, on the trb ml.
(asciilifeform) asciilifeform: bvt: getdata will issue req. for block hashes drawn from this set .
(asciilifeform) asciilifeform: curiousd0g: the docs for trb, to the extent they exist, are on tbf www and mailing list .
(trilema) asciilifeform: ( imho 'makesnap' oughta also be considered, but admittedly may be of 'niche' interest )
(trilema) asciilifeform: !Q later tell phf plox to snarf http://therealbitcoin.org/ml/btc-dev/2018-October/000315.html into 'experiment' tree.
(trilema) asciilifeform: for moar complex/auto-restarting example, see also http://therealbitcoin.org/ml/btc-dev/2017-February/000252.html article
(trilema) asciilifeform: oughta be same procedure as http://therealbitcoin.org/ml/btc-dev/2018-April/000296.html , but in the tool, imho.
(trilema) asciilifeform: PeterL: as i currently understand : yes. but ideally this simple mechanism would be in the tool, rather than a http://therealbitcoin.org/ml/btc-dev/2018-April/000296.html - style shell hack.
(trilema) asciilifeform: http://therealbitcoin.org/ml/btc-dev/2015-July/000107.html << for reference, recipe for graphic process mem usages
(trilema) asciilifeform: mircea_popescu: he actually baked a patch, about same time as my aggression item, http://therealbitcoin.org/ml/btc-dev/2017-December/000282.html
(trilema) asciilifeform: phf: right, i grasped this, hence why i wrote a demo impl of trinqueian algo ( http://therealbitcoin.org/ml/btc-dev/2018-April/000296.html ) which actually does solve it
(trilema) asciilifeform: the 'is it same trb' is much smaller problem than it seems, is quite resolvable mechanically ( as demonstrated in my http://therealbitcoin.org/ml/btc-dev/2018-April/000296.html experiment , for instance )
(trilema) asciilifeform: just about errything that doesn't abuse some glibc-specific knob, runs 100% under muslism ( e.g. trb, which was the first proggy i personally built for musl, back in the http://therealbitcoin.org/ml/btc-dev/2015-July/000133.html days )
(trilema) asciilifeform: trinque: imho your approach is the correct one -- similar to http://therealbitcoin.org/ml/btc-dev/2014-October/000003.html , first pin down , then -- shaving.
(trilema) asciilifeform: this -- is true. scripting lang, however, has a place in life outside of wwwism -- for throwaway experiments, e.g. http://therealbitcoin.org/ml/btc-dev/2018-April/000296.html , and similar
(trilema) asciilifeform: mod6: see also the simpler example in the orig post , http://therealbitcoin.org/ml/btc-dev/2018-March/000293.html .
(trilema) asciilifeform: trinque: didja ever get a chance to try the algo i demo'd in http://therealbitcoin.org/ml/btc-dev/2018-April/000296.html ? what did you think ?
(trilema) asciilifeform: !~later tell mod6 http://therealbitcoin.org/ml/btc-dev/2018-January/000285.html << i noticed, somehow only nao, that it has text 'This experimental vpatch requests blocks from all nodes that send a version message.' >> which has 0 relation to the patch...
(trilema) asciilifeform: interestingly , this item was the 2nd thing asciilifeform ever genesised ( http://therealbitcoin.org/ml/btc-dev/2015-October/000175.html ) . 1st was trb.
(trilema) asciilifeform: mod6: see ye olde http://therealbitcoin.org/ml/btc-dev/2015-July/000107.html << there is a pythong and gp script in there
(trilema) asciilifeform: ben_vulpes: http://therealbitcoin.org/ml/btc-dev/2015-January/000033.html << arm cross-flags example (from ye olde trb)
(trilema) asciilifeform: also http://therealbitcoin.org/ml/btc-dev/2017-February/000252.html has typo! and nobody noticed!!1 chown oughta be, of course, chmod.
(trilema) asciilifeform: adlai: any time you feel like doing something useful -- no shortage of items. there is, for instance, a trb knob direly needing testing, http://therealbitcoin.org/ml/btc-dev/2017-February/000251.html
(trilema) asciilifeform: ;;later tell jurov i recently dug up your oldie, http://therealbitcoin.org/ml/btc-dev/2015-December/000186.html , and had a thought: did we ever investigate why, e.g., 0.8+, doesn't leak ?
(trilema) 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.
(trilema) asciilifeform: mircea_popescu: http://therealbitcoin.org/ml/btc-dev/2015-August/000145.html << good example of how to use turdatron. click on the links to see each of the three attachments verbatim.
(trilema) ascii_field: mircea_popescu: http://therealbitcoin.org/ml/btc-dev/2015-August/000161.html << possibly also this set of example
(trilema) asciilifeform: importantly, these need to be detached (own file) signatures. specifically ~not~ like this: http://therealbitcoin.org/ml/btc-dev/2015-August/000150.html
(trilema) asciilifeform: http://therealbitcoin.org/ml/btc-dev/2015-August/000150.html << FOR FUCKS SAKE which one of you is 'pub@extemporized' ?
(trilema) asciilifeform: http://therealbitcoin.org/ml/btc-dev/attachments/20150819/genesis_2cba721ced8108cf65ab7d045081237ecda4602a.vpatch << seeing 'chicken' all in one file sorta reminds me that the thing is finite and pretty small, and can be grasped. almost.
(trilema) asciilifeform: http://therealbitcoin.org/ml/btc-dev/2015-June/000100.html << example of one of my patches listing antecedents
(trilema) asciilifeform: who does not believe, is welcome to go and try the experiment in http://therealbitcoin.org/ml/btc-dev/2015-August/000142.html
(trilema) asciilifeform: looks like trinque forgot to link his patch here? >>>> http://therealbitcoin.org/ml/btc-dev/2015-July/000136.html <<<<
(trilema) asciilifeform: danielpbarron, mod6, anybody with a SYNCED 0.5.x node: please consider blkcut ( http://therealbitcoin.org/ml/btc-dev/2015-July/000113.html ) -ing your most recent blkxxxx and uploading a tarball of the last 500 or so blocks
(trilema) ascii_field: http://therealbitcoin.org/ml/btc-dev/attachments/20150701/pss_2f32fc9570f505a65c46b118c415cae70d57d757.png << in other news, one can infer that bitcoin permanently sits down on ~300 byte per block ingested
(trilema) ascii_field: Jautenim: we already have the install_sw thing - see http://therealbitcoin.org/ml/btc-dev/2015-June/000102.html
(trilema) asciilifeform: Michail1: see also http://therealbitcoin.org/ml/btc-dev starting from feb.'15
(trilema) asciilifeform: ben_vulpes: feel free to lift the ascii jolly roger from http://therealbitcoin.org/ml/btc-dev/2015-January/000038.html for the warning banner...
(trilema) asciilifeform: ben_vulpes: out of curiosity, what's the elisp doing in http://therealbitcoin.org/ml/btc-dev/2015-March/000070.html ?

|