asciilifeform: i've contemplated attempting an openwatcom build of trb.
asciilifeform: as happens many times every day on our trb nodes.
asciilifeform: mircea_popescu: the 'segwit' thing is, as i understand, intended as a protocol hardfork - to isolate trb users.
asciilifeform: there will (and perhaps already are) a multitude of chumpers who believe they have X btc, while really they have some quantity Q, possible 0, of actual btc, and X-Q of gavinola, which consists of tx, somehow elaborately processed, that trb rejects as noise, and display as wtf 'shot into the sun' crapolade in any civilized block viewer
mircea_popescu: trb is however distinguished by being the most acceptant. so...
asciilifeform: this piece was put in as attempt to disincentivize connection to trb nodes.
mircea_popescu: miner runnign trb-esque thing only would not, right. the first gets cut off because fees, the second because unknown inputs.
asciilifeform: mircea_popescu: as i understand, PeterL was pointing out that trb does not relay the ingredients desired in this kitchen.
asciilifeform: phf: the 'grabs a broom and a bucket and cleans it' incidentally is more or less the story of my 1st year of trb.
asciilifeform: shinohai: even trb will run for no more than 2-3 weeks on 2G.
asciilifeform: jurov: aha, and those are the 5 people who have any business patching trb.
mircea_popescu: anyway ; it's evident that in the future republican code will have one of the two possible profiles (trb-like ; eulora-like), not necessarily one, and certainly not necessarily the former.
asciilifeform: as trb does.
asciilifeform: as trb does.
asciilifeform: mod6's trb-builder.
asciilifeform: and trb - its own. etc.
asciilifeform: e.g., mod6's vtron does not depend on trb in any way shape or form
asciilifeform: not only trb.
asciilifeform: it is still the authoritative history of trb.
asciilifeform: this would be a handy (optional) item to have in trb.
mircea_popescu: heh. aaand a trb node is at height 419220 for absolutely no reason ; 50+ connections, stable etc.
asciilifeform: he trb'd it.
asciilifeform: he solved it the trb way.
asciilifeform: sorta like we did with trb.
asciilifeform: iirc it was the db descriptors thing in trb.
asciilifeform: nor could ever, with trb.
asciilifeform: it is about miners spitting on a perfectly valid, per trb rules, tx
asciilifeform: ~0 hashrate behind 100%-everything-trb-will-happily-eat protocol breadth
asciilifeform: so long as trb node accepts a hypothetical block as valid, it is mineable.
asciilifeform: (if this, they will eventually be candidates for anal reeducation, just as we would have been sans trb)
asciilifeform: so... has an 'eth trb' yet appeared ?
asciilifeform: trbbot?
asciilifeform: box also hosts the only (afaik) 'five nines'-reliable trb node.
asciilifeform: not any dumber than mitming my trb node.
asciilifeform: the same sense the behaviour of my trb node's upstream makes.
asciilifeform: and in many cases, in particular the one now contemplated, is wholly unnecessary: fetching the trb deps is a once-per-machine thing
asciilifeform: http://btcbase.org/log/2016-07-14#1502685 << what has mircea_popescu been smoking?? there is no qt in trb
mircea_popescu: it seems to me they should be in trb tree. which tradeoffs do you see ?
asciilifeform: ;;later tell mod6 http://thebitcoin.foundation/trusted-nodes.html << is missing dulap, the single most robust trb node i know of
asciilifeform: i'ma install it trb-style
asciilifeform: trb? trinque made one
asciilifeform: mod6: i was damn sure there was a draft cookbook but i slept through it, and it was not yet posted to trb www.
asciilifeform: soooo it appears that we do not have ~any~ recipe posted for building vtronic trb ?
asciilifeform: ;;later tell mod6 the link in trb.foundation STILL POINTS TO BITCOIN-ASSETS WIKI
asciilifeform: http://btcbase.org/log/2016-07-04#1497206 << my original recipe still worx and will always work. use a recent trb tho.
asciilifeform: we dun even have 3 reliable trb nodez.
asciilifeform: anything other than unconditional capitulation to trb, == prb.
mircea_popescu: trb acted correctly.
asciilifeform: i disagree that the enemy ought to have any say in how trb works.
mircea_popescu: trb has no notion of "coin history". nor should it. because taint is not a thing.
mircea_popescu: i don't see trb should do anything. i also don't see why any sane person would continue dealing with any entity using it.
asciilifeform: and pieces of shit, e.g., https://wiki.openwrt.org/_media/media/tplink/tl-mr3020/tl-mr3020_top-pcb-gpio-pins.jpg?w=400&tok=e00072 << as i once experimented with for trbification << have dram.
mircea_popescu: so really, either iB or outright TRB will have to have an auth layer for nodes.
asciilifeform: trinque: it was how we genesis'd trb, recall.
asciilifeform: i am NOT and will NOT be willing to sign off on, e.g., tinyscheme, or even trb, with same level of assurance as for code that i and i alone had written.
mircea_popescu: i personally never got the idea it's part of trb or anything. seemed to me more like a "alf's other project", sort of like the ffz thing.
asciilifeform: 1) trb-genesis
asciilifeform: as would be the case in a mircea_popescuated shiva trb.
mircea_popescu: mod6 : if you're building trb, you start from a trb genesis. if you're building V (via V), you start from a V genesis. and so on.
asciilifeform: trb-genesis, and shiva-genesis.
asciilifeform: http://btcbase.org/log/2016-06-13#1481822 << mircea_popescu made a very convincing argument in favour of ~not~ having a central repo of any kind, but rather - if anything - a streamlined mechanism for each lord (including mod6 & ben_vulpes under the banner of trb foundation) to put ~his own trb~ in usable format on ~his own~ www
asciilifeform: ;;later tell mod6 if i want trb i don't need to ask for '/trb/whateverthefuck-fixes-retardation.vpatch', asking for whateverthefuck-fixes-retardation.vpatch must suffice !
mircea_popescu: so you cd trb and it takes you to it.
mircea_popescu: none of this "trb". just make a dir like /7ad78d387187350 or w/e
asciilifeform: ;;later tell mod6 'It has been well established that OOM error occurs from bastards not being freed from memory.' << not accurate. bastard tx don't enter the mempool in trb. it is mempool tx that never deallocate...
mircea_popescu: mod6 http://thebitcoin.foundation/tickets/trb_ascii_graph.txt << ideally numbers should be hooverable, ie show ticket content if you put mouse on it. title="$ticket" iirc.
asciilifeform: do you recall my attempt at forcing trb to flush its mempool?
asciilifeform: http://btcbase.org/log/2016-06-04#1476897 << mod6 i was talking about the stator.sh in the tarball distributed on therealbitcoin.org. but more generally speaking we should NOT be linking to openssl.org or other heathens! the tarballs are not so big, they ought to be on trb site.
asciilifeform: ;;later tell mod6 the openssl people hosed your stator script by moving their turdball without a redirect. can we plz stop linking to derps in trb autoloaders ?
asciilifeform: the memory leak will still have to be killed though, before these can trb.
asciilifeform: or whether the trb on the box is worth using any moar
asciilifeform: phuctor, trb
asciilifeform: farewell 136+ day trb uptime
mircea_popescu: basically some usg assholes tried to hijack the bitcoin. trb aka the real bitcoin is the... well, the real bitcoin.
mircea_popescu: tell you what : i'll buy that, and pay it in advance for a year, provided you install and manage a trb node there.
asciilifeform: it was the trb source callgraph
mircea_popescu: ah yeah. i think we'll need to make a "min 4gb ram for new boxes" tmsr standard ; so people can run general purpose + trb on them
asciilifeform: i've wondered often who precisely they paid, and how much, to set up even a basic 'first 6mo of trb'-level framework for them of understanding how the shitsoup even worx
asciilifeform: i'd be curious, though, to meet a usg fauxtoshi who is willing to endure 5 minutes of my questions re trb src.
mircea_popescu: asciilifeform but in a discussion of indian tribes, the smaller trbie with guns that wipes the larger tribe with tomahawks HAS, in fact, deployed the technology.
asciilifeform: http://trilema.com/2013/the-future-in-the-past << great vintage mircea_popescutronic lul re trb...
asciilifeform: trb on dulap up for 127 d, 17h, 30m, contiguous; current footprint == ~8G.
asciilifeform: dulap (nosuchlabs.com, but recall we have no dns, it is 46.166.165.30 for trb purposes)
asciilifeform: (in practice, trb node on a decent box like dulap can run for a very long time - years - without reset)
mircea_popescu: asciilifeform lol trb nodes still oom. darn.
asciilifeform: http://btcbase.org/log/2016-05-16#1467378 << i must point out that, at least on same nazi site, the count of trb nodez is also record low - 5
asciilifeform: what can i do, even my trb hasn't restarted since december
asciilifeform: my vtron was very much a battlefield wunderwaffen, adequate strictly for pressing a well-gardened trb tree that consisted 95% of asciilifeform
asciilifeform: e.g. trb and dns.
asciilifeform: ;;later tell jurov observed any spike in trb site traffic ? (it is linked from nosuchlabs.com)
asciilifeform: but this includes, e.g., trb.
mircea_popescu: yeah but trb really doesn't load worth the mention. especially if caught up.
asciilifeform: recall it is also trb.
asciilifeform: where, i suspect, the only folks able to connect to the trb node on same box are also us.
asciilifeform: (does anyone still recall how trb was originally something i asked nubs to make!)
asciilifeform: after departure of nubs, who will print trb!1?111
asciilifeform: unrelatedly, trb has been up for 100+ consecutive dayz there.
asciilifeform: trinque: same place as the lag on my trb nodez
mircea_popescu: i think for some reason you got the idea that if mp gets phuctor server it's ok to come in, redefine it as "trb node" and move on.
asciilifeform: <mircea_popescu> including five straight months of 1/4 gb ram box at close to a btc/month pulling our dicks. << that thing incidentally has been the ONLY public trb node that has never fallen down. not once.
asciilifeform: and yes, i ported trb to arm. as wartime wunderwaffen (which went nowhere.)
asciilifeform: (or from trb at any rate, iirc mod6 had this in his original diagrammator)
mircea_popescu: asciilifeform the relationship between sane bitcoin source as available on trb www and "bitcoin" is THE SAME as the relation between a sane implementation of tetris and "running tetris"
asciilifeform: mircea_popescu: trb's www
asciilifeform: ;;later tell mircea_popescu i had a notion: if we're no longer holding the 'father's pistols' line, is there any good reason not to replace openssl in trb with, e.g., ada bignum ?
asciilifeform: mircea_popescu, ben_vulpes, mod6, et al : did jurov stop working as trb treasurer , coinbr operator ? i must have missed this ? 'cause i dun see him in the mircea_popescutronic list
asciilifeform: next we calculate how many sheets of toiler paper trb fits on, etc.
asciilifeform: in other nyooz, the immunocompromise thing was accurate, already folks who oughta know better, on old planet, asked me if i'd host a powerranger idiot repo 'for trb'
asciilifeform: there are reasons why my first act re trb was to exterminate all compatibility with microshit
asciilifeform: and this is a patch without which trb is ~dead in the water~
asciilifeform: it was EMINENTLY possible to build trb pre-v.
asciilifeform: (rotor invokes boost's jam thing but trb, recall, builds with ordinary gnumake)
asciilifeform: http://log.bitcoin-assets.com/?date=19-03-2016#1436543 << there is no provision for anything of the kind in trb, beyond the barbaric expedient of a tx which throws exception during processing simply not being stored
asciilifeform: thestringpuller: nope, the only genuine solution would be multithreaded trb
asciilifeform: in related nyooz, i discovered that one of my test trb boxen has been wedged, without any meaningful log noise whatsoever, for ~2wks
asciilifeform: and contemplating trbtronics, rather than praying to vishnu ?
mircea_popescu: even historical order would acvtually beat trb on this.
asciilifeform: which is what we have in trb
asciilifeform: wallet (incl. trb) ~much~ dislikes doublespends
mircea_popescu: so your idea is, that we of course continue to maintain trb as is, but also develop a keccak pow variant, for use in case of forks ? or vice-versa, in case of forks develop it ?
asciilifeform: keccak-clean and keccak-trbchain.
mircea_popescu: at no point was it proposed that trb does.
mircea_popescu: adlai wouldja think for a moment ? if miners fork tomorrow, pre-miner-fork trb will not be defensible. because bitfury (you know, kakobrekla's friends) have access to vc capital, and will bridge the gap between us printing press and chinese mining.
asciilifeform: or introduction of material from either into a future trb
mircea_popescu: so basically you propose - wait and see on trb, meanwhile i'll also develop a fork variant which i won't either share or have ready in time ?
asciilifeform: i will maintain trb, while 1,001 things incl. writing mine.
asciilifeform: if trb gets chainclobbered - it is 2009 again for us.
mircea_popescu: so in this sense, "trb as is only" opens us up to being forced, later on, to pick among the idiots.
mircea_popescu: there is a very specific danger which you perhaps are not seeing. if indeed we continu with trb as is, and if indeed 3) happens, as these two share pow and we don't control .7 or so exahash we become extremelty vulnerable. recall the fate of altcoin ?
mircea_popescu: but you should note, that there is no good reason to consider current trb so much different from cases 1-3.
mircea_popescu: in any case trb isn't going anywhere, nor need it go anywhere.
mircea_popescu: at this juncture, tmsr must make the decision if it will continue strictly with trb, or ALSO offer a tmsr fork of trb.
asciilifeform: and where did trb go ?
asciilifeform: jurov: it is for working on trb !
asciilifeform: i was willing to deal with the cpp miseryu of trb because 1) it pre-dates bitcoin being valuable 2) it was - and remains - the schelling point, 'father's pistols'
mircea_popescu: in other news - it still remains likely that this summer will see a bevy of various hardforks on offer. practically speaking, trb can offer either its own candidate, which takes a lot of work, or else sit tight and we'll follow the more intelligent of the avaialble offerings, which takes less work but also implies a lot of risk - experience to date shows that there's precious little intelligence available outside the w
mircea_popescu: trinque> rather than dissect it, I wish to stop using the wallet entirely (as I did before with btcd) and just write a sendrawtxn for shiva <<< a raw tx manipulator for trb is prolly a very useful item, really.
asciilifeform: so i go and send on another box and guess what, it had previous trb, and tx is high-s.
asciilifeform: that trb chokes on, during rescan, and quits.
asciilifeform: the ~only thing i know about mpb is that 1) it is roughly compatible with 0.6 and 2) he fixed the db locks bug years ago, and shared with me the patch, a while back, and it is in trb
asciilifeform: and certainly not trbtronic ones.
asciilifeform: if your client barfs when working with trb, patch your client.
asciilifeform: dooglus: when trb disagrees with prb, prb is ipso facto wrong.
asciilifeform: http://log.bitcoin-assets.com/?date=07-03-2016#1424721 << this is not actually correct, it should build only gcc and toolchain, then trb.
mircea_popescu: !rate dooglus 2 ran one of the best dice sites of all times, before being torpedoed by fiat government posturing. trb testing.
mircea_popescu: mod6 even if - and consider i'm speaking of a purely cartoon view of reality, merely for illustration purposes - even if trbf "misses the boat" and instead dilligently focuses on fixing satoshi code, and three years later the "winner" of july competition falls on sword that trbf actually fouind and fixed, the relative position of trbf in the world has not suffered one iota.
mircea_popescu: what do you expect changed with trb ? you weren't doing it to get rich, were you ? you weren't doing it for redditettes to throw their panties at you, were you ?
asciilifeform: except that i have nfi what we're doing with trb.
mircea_popescu: note that my interest in computers is, these days, ~strictly predicated on trb.
mircea_popescu: mod6 your call to make, together with ben_vulpes i guess - the point remains, if no trb offering in july, no trb offering in july.
mircea_popescu: i suppose IF the july many-fork time comes and trb has nothing to offer then it might as well close.
asciilifeform: so trb foundation closes today?
mircea_popescu: ideally trb will at that time be ready to propose one of its own.
asciilifeform: jurov: works great in practice. in your trb node.
asciilifeform: could far more easily declare, as trb does, 'tx is only valid if inputs are confirmed in existing block.'
asciilifeform: sturles: it is pointedly NOT 'how it is' in trb.
asciilifeform: trb does not deal in mights.
asciilifeform: sturles: trb WON'T ACCEPT a tx with even ONE unconfirmed input.
mircea_popescu: anyway, if you're curious, what trb is contemplating to eventually do is a ring buffer with a per-kb fee only as the criteria.
asciilifeform: run moar trb.
asciilifeform: i have 3-4 trb nodez going, just on house lan, at all times, so backup sorta solves itself.
asciilifeform: shinohai: i think it is interesting that i've been kill -9 'ing trb since day 1 and never had this problem.
asciilifeform: jurov: and to the extent i blow my very little free time on trbism, they are.
asciilifeform: mircea_popescu: trb didn't even get off the runway until magic constants, recall.
mircea_popescu: i distinctly recal trb nearly sunk in the other incident, while mpb provided the magic constants. why was that ?
asciilifeform: i distinctly recall that trb sailed through the july incident while mpb did not.
mircea_popescu: which aren't, at the present time, trb-tethered. it's a goal, but into the future.
mircea_popescu: kakobrekla> one thing that goes through my mind is that trb/mps << this is true, but let me clarify that An set of txn were broadcast through a set of > 1k distinct peers. most of which i don't regard as peers in any sense, but nevertheless they did get to hear about them from my own nodes.
mircea_popescu: kakobrekla and guess what - trb gets blackholed now and again. prb never mattered.
asciilifeform: not related to dulap except in the fact that both are trb nodes.
asciilifeform: mircea_popescu: dulap is not only platform for phuctor, but will host 'g', gossip, etc., and is presently the largest and most reliable trb battleship. and i will pay for it personally, because wtf.
mircea_popescu: asciilifeform i was tempted throughout eulora lifetime to go "fu, no binaries, compile, always". and i can still contemplate why this would be the case with trb.
asciilifeform: i don't recall a ~rotor~ trb working there.
asciilifeform: anyone ever build a working trb on openbsd ?
asciilifeform: i'm beginning to understand why the enemy is not particularly scared of trb.
mircea_popescu: !s trb
asciilifeform: 1) press a trb
mircea_popescu: no. the goal of trb is to be ran AMONG PEOPLE.
asciilifeform: mod6, ben_vulpes, mircea_popescu, et al : possibly a neglected subject in the wiki, trb site, etc. is where the hell a n00b is supposed to get pubkeys.
asciilifeform: mircea_popescu: ftr, about 1/2 of a stripped trb binary is openssl crud that is never called.
mircea_popescu: for all you know, i peer with a "network at large" node, making it thus trb-node-one-removed.
mircea_popescu: phf the separation between "trb nodes" and "the rest of the network" comes of the same sort of usg-enabling fiction where somehow obama owns the land and i live on it by his permision.
asciilifeform: all i can say is that i have nfi. but i have no evidence that anyone other than mircea_popescu and trb folks did any serious re-engineering re: the client.
asciilifeform: so far the only 'alt-trb' for which i have any evidence whatsoever of its existence is mircea_popescu's thing
asciilifeform: trinque: however you try to dance around the problem, must come to terms with the fact that ~some~ trb nodes must talk to the heathens ~some~ of the time, or NO BLOCKS
asciilifeform: 'A fully virtualized “Hello World” service in IncludeOS (which of course includes the necessary components of the OS) uses only 8.45MB of memory. A Ubuntu 14.04 OS image (the default guest OS for OpenStack) is around 300MB by comparison.' << idiocy. i had linux kernel AND trb in < 5 MB.
mircea_popescu: eh it doesn't pull anything. think about it : it is a modest, quiet hope, specifically that shiva/b-a/trb is actually heavy enough that it may pull him.
mircea_popescu: won't be accepted in trb by any means, but i dun see anything wrong wiht the process.
asciilifeform: phf: http://log.bitcoin-assets.com/?date=21-02-2016#1412300 << as stated in the comments, i regard this as a serious loose end that must be tied before anyone can even contemplate using a shivatronic trb in the battlefield
asciilifeform: (for n00bs or readers who have not been keeping up, 'shiva' is a highly experimental affair and not to be considered part of mainline trb!)
asciilifeform: 1) to have the cpp content of trb asymptotically go to ZERO with time
asciilifeform: is that by 'marshalling' the pointers, you are introducing trb's leakages into tinyscheme.
asciilifeform: shiva.cpp as i originally wrote it, includes all of the trb headers. you can form scheme data structures handily without engaging in weird cppisms, just by iterating over, e.g., the node list, and forming scheme list while you do it.
asciilifeform: aha recall this from early trb days ?
mircea_popescu: but the point remains : having a trb foundation on the solid foundation of a v environment IS a convenience.
asciilifeform: mircea_popescu: this is a defensible perspective but it leaves me wondering wtf you were doing when founded a trb foundation ! a throne omg!!1111111
mircea_popescu: and i would very much like it be the case that some folks here actually want to specifically trbn
mircea_popescu: this whole "we are developers herp" thing is prb not trb.
asciilifeform: on the other hand, a bunch of folks here are trying to trb
asciilifeform: ~6G occupied by trb on dulap after 40 days. nb.
asciilifeform: in other news, blocks that take my trb nodez 5-10 min. to verify have become sop.
asciilifeform: it is one thing if it is a heathen dep that pre-existed trb, e.g., boost
asciilifeform: (the folks who laughed when i said 'no curl on trb build box' - still laughing ?)
asciilifeform: part1 is the bridge. part2 is the only place where trb per se is touched, where the hooks are inserted.
asciilifeform: http://log.bitcoin-assets.com/?date=17-02-2016#1408030 << it had own genesis to establish pedigree with the historic tinyscheme. but shiva is a patch that bridges it into the trb tree. and yes i rebased it, it works with the current trb.
asciilifeform: a blackholed trb does not fall silent, but actually is maintaining links with a number of existing peers (bouncing inv's, etc)
asciilifeform: Stec: you need gcc on any reasonable unix. that's all. trb will build a new compiler, and with it will build itself.
asciilifeform: Stec: let us know if you have any problem building trb.
asciilifeform: fella says he wants to try trb.
asciilifeform: Stec: рекомендую познакомиться с исходиками trb, не пожалеешь
mircea_popescu: Stec are you running trb on them ?
asciilifeform: incidentally i see no reason why any trb node ought to allow a tx (mempool, vs in-block) to consume more cpu time than it took to receive from the nic.
asciilifeform: BingoBoingo: every time trb is mentioned on reddit, i see this crud re: 'important fixes.'
asciilifeform: BingoBoingo: the blackout re: trb is more or less total, don't expect miracles
asciilifeform: BingoBoingo: i would add in your article that the flagship trb boxes are running sans-glibc.
mircea_popescu: now that trb no longer uses it, is ok to burn it ?
asciilifeform: does pywallet actually work with trb ?
mircea_popescu: !rate shinohai 2 Active TRB tester guy.
asciilifeform: which ~trb~ mircea_popescu ?
asciilifeform: not trb
asciilifeform: and yeah there is no question of running trb on this.
asciilifeform: you can't trb-develop on the x60.
asciilifeform: on an isolated lan, place trb nodes, and break all known blocks into tx,
mircea_popescu: having a trb-test suite is a good move, because even if dissidence is a b-a tradition, nevertheless it allows a common basis to make communication useful.
asciilifeform: this might be a productive approach for trb
asciilifeform: one tricky bit is that trb is a ~system~
asciilifeform: trb is alive, v is a knife.
mircea_popescu: trb is alive whether you want it or not.
asciilifeform: http://log.bitcoin-assets.com/?date=09-02-2016#1400190 << trivial - if trb marks a tx nonstandard - it is nonstandard!11
asciilifeform: where, say, 0 is maximally permissive (disables malleus, even) and 10 is 'any sign of deviation from trb conventions --> permaban'
asciilifeform: this would walk the razor's edge of danger, in re splitting trb into own parallel universe, however
mircea_popescu: maqp i suppose you could look into TRB. get yourself V and make your own secure node.
mircea_popescu: i dunno what it is, i've never seen it before trb myself, nor a really good one since.
asciilifeform: 5x19x141x248.static-customer.iz.ertelecom.ru << in mircea_popescu's trb fleet ?
mircea_popescu: trinque> also, I don't see sendrawtransaction in trb's list o' commands... wat do? << cry all the way home, we don't have it yet. backport it ? :D
asciilifeform: tinyscheme genesis is NOT PART OF TRB !!1111111111111
asciilifeform: it is my intention to do this to trb.
mircea_popescu: if you produce a mythical man-month's code for trb, that adds the accounting value of a man-month to the tmsr gdp whether you mean for it to or not.
mircea_popescu: ascii_rear> but eventually we ought to be able to do spiffy things like writing my memory usage grapher ~entirely in shiva~, etc << quite. once this is fully functional debugging in trb can not be matched, period. by anyone, anywhere, doing anything.
mircea_popescu: incidentally, speaking of config setups : 1. pick a list of TRB nodes ; 2. add to ifconfig, deny all others ; 3. plug eth cable, congrats, you now have a secure box. go ahead install all the toolbar spyware you care to, won't matter.
mircea_popescu: not like if trb.buildroot pops up tomorrow i wouldn't at least consider it.
mircea_popescu: you wanna write trb by hand on stone, fine.
asciilifeform: but in all seriousness, a battlefield trb oughta be built on a virginal airgapped box.
mircea_popescu: im actually curious which happens first, trb hardware delivery or cn hardware delivery.
asciilifeform: (and if it takes 100 hours to build motherfucking trb, it is NOT a workstation!)
mircea_popescu: and also, could we bundle a pre-created .conf file with the release ? something to include say all the public trb nodes as -connects and stuff, with a comment to explain to people how to turn it into a public node ?
mircea_popescu: PeterL probably. moreover, it allows the trb network to be built in depth. what the fuck do we even have the fronteer nodes for if not to protect us
mircea_popescu: mod6 : latest trb v99996 on 91.218.246.31 says "blocks" : 4500, "connections" : 13,