Show Idle (> d.) Chans
← | Results 1501 ... 1637 found in trilema for 'f:ifeform f:escu trb'
mircea_popescu: mod6 your latest pressing away on a new system. will announce it and add to trb fleet once done.
mircea_popescu: <phf> asciilifeform: check it http://glyf.org/tmp/trb-transition.png << p neat, but why is the shiva stuff connected ?
mircea_popescu: consider the epic failuire of private messages to gather import or relevance in the trb and you;'ll have a fine illustration of why multiband is retarded.
mircea_popescu: trbtcd neh ?
mircea_popescu: hanbot hey were you making a trb current build ?
mircea_popescu: i'm quickly building a reputation for a wrecker of trb aren't i !
asciilifeform: for trb?!
mircea_popescu: "we're narrowly intelligent but broadly speaking stupid, we were raped for our ineptitude by some nobody that mp trampled underfoot without even particularly noticing. really - go use TRB, we'll just follow along quietly to try and learn something"
asciilifeform: so now i gotta write an elisp for trb
asciilifeform: as for prb, it doesn't like talking to trb (esp. with the malleus patch)
asciilifeform: char *p = sc->strbuff;
asciilifeform: while ((p - sc->strbuff < sizeof(sc->strbuff)) &&
asciilifeform: anything you say in 'private' about trb will generally end up having to be repeated at least once.
asciilifeform: so you can meaningfully probe the living trb
asciilifeform: polarbeard: based on trb.
asciilifeform: in trb.
asciilifeform: tinyscheme welded onto trb
asciilifeform: it is bad enough that trb has 500 man-year of study baked into it. let's now add a 501st ?
mircea_popescu: http://log.bitcoin-assets.com/?date=23-01-2016#1382232 << even the simple step of "add flag to trb to dump mempool into file each time a block is found" would be helpful atm.
asciilifeform: polarbeard: in case you did not know, you can browse the almost-current trb using www browser, http://btc.yt/lxr/satoshi/source?v=asciilifeform_maxint_locks_corrected
asciilifeform: polarbeard: how did you come upon your interest in trb ?
mircea_popescu: trinque i suspect this is what drove alf's ideas of you know, deliberate sabotage against trb nodes.
mircea_popescu: nevertheless, the bit is in the horse's mouth : trb will be more read than wrot.
asciilifeform: trb has papercut on one arm, gangrene in the other.
mircea_popescu: incidentally, and unrelatedly to the "magic numbers" avenue of trb improvement : one obvious anbd cheap hardening for trb would be to allow the user control of entropy source.
mircea_popescu: so i'm guessing... another 2-3 weeks for full sync, making a trb full sync take just about two months on a reasonable box.
asciilifeform: boost is used in trb for iterators, for the most part
asciilifeform: incidentally not so long ago i felt the desire to rewrite chunks of trb to abolish boost
asciilifeform: if trb is sleeping in a dumpster and picking old razors out of the rotting mcd 'meal' trays to eat, prb is drowning in a usg paper dump
asciilifeform wonders what moved mircea_popescu to try his hand at trbism
asciilifeform: until recently i used this www for just about all trb study
asciilifeform: this is one of the things that distinguishes trb from heathenb
asciilifeform: mircea_popescu: fwiw i'm heavily in favour of the 'fix only the lines we touch' school of thought. the whole point of pedigreed-vintage trb is that the totality of the changes we made is apparent to the naked eye.
mircea_popescu: !rate mod6 5 His curative TRB leadership is a shining beacon for the entire Republic.
asciilifeform: the spaces thing is just one in 10,001 sad things in a jupiter-sized ball of sad that is trb.
asciilifeform: fwiw i've deliberately refrained from munging whitespace or even fixing the asinine { } convention used in trb
mircea_popescu: heh. the imf has no trb mandate, nor will it.
asciilifeform: the second mode is what all of my trb boxen are set to, and it results in a comedy where the thing routinely drops friends on the floor and dallies about attempting to connect to randomly-selected derp ips
asciilifeform: presently trb does not have this sane behaviour
asciilifeform: http://log.bitcoin-assets.com/?date=19-01-2016#1377917 << i must point out that the whole 'seeding' concept - as contemplated in the dark ages pre-trb client - is profoundly braindamaged.
mircea_popescu: PeterL this is a public channel. for obvious security reasons trb is a superset thereof.
asciilifeform: rather than adding talmudistry to trb
mircea_popescu: iirc mod6 was considering a trb patch
mircea_popescu: anyway. this bullshit won't be either mined or relayed by trb.
asciilifeform is watching the scrolling logs from his trb nodez, it is like music, so smooth
asciilifeform: ;;later tell BingoBoingo it is not an accurate description of malleus patch to say that it only nukes peers using bloom filters. it nukes any peer which issues any command whatsoever unsupported in trb.
asciilifeform: ~considerably~ smoother performance on the trb+malleus nodez
mircea_popescu: http://log.bitcoin-assets.com/?date=11-01-2016#1366063 <<< certainly. which is why trb nodes are not all advertised, and we're eagerly awaiting seeing this "pure coincidence".
asciilifeform: ben_vulpes: i have an openbsd box here but it will not build trb, not enough ram (+swap even)
asciilifeform: http://log.bitcoin-assets.com/?date=11-01-2016#1365915 << remind me again why you have a sideshow thing and not trb
mircea_popescu: i would strongly advise anyone using trb in production to at least test this patch.
asciilifeform: (iso that booted to trb)
asciilifeform: generally you will see this in trb if you built for $machine but you have $othermachine.
mircea_popescu: i recall hav ing a 32 bit trb made to work at some point, but not the specifics
mircea_popescu: or did you make the os 32 and trb 64 ?
mircea_popescu: adlai if you can code, you can actually help the trb people. if you can't code, you can try an' help BingoBoingo, who's coinstantly asking. or else offend copypaste by rewriting trilema as best you can. or etc.
mircea_popescu: what they like it for - to save in, as per http://trilema.com/2014/la-florida-and-other-places/#selection-109.0-109.542 - is readily satisfied by trb as it is.
asciilifeform: that there is not a trb path between my nodez and the miners.
mircea_popescu: it should also not be the case that there isn't a trb path between you and miners.
mircea_popescu: miner defection from any and all non-trb approved soft forks is a ~GUARANTEE~ in the future. just a question of when.
mircea_popescu: sooo... acthung panzers, asciilifeform ben_vulpes mod6 : it is certain beyond any conceivable doubt the trb nodes are isolated - both the publicly advertised ones and at least one not publicly advertised, because lo! what used to be tx e6b8aa9dedef74a7e8961e0d997aebc35aae3c8e762a715336d84b39507c9773 has not only been successfully broadcast but it got malleated, and is now included in the chain as c29e162c79144ced3e827
mircea_popescu: punkman mno. that is an unrelated issue of a 2nd tx. again, it's not surprising, seeing how trb handles chains.
mircea_popescu: punkman we know for a fact everyone in trb DOES have it in their mempool, actually.
mircea_popescu: mno, they accepted one and rejected the rest (which is unsurprising for trb, seeing how the rest were chained on the one)
mircea_popescu: i've been broadcasting it all night to the trb nodes, you can ask any of them, they should still have it in the memory.
asciilifeform: ;;later tell mircea_popescu understand that, for while there are only a few trb nodes, and everyone knows where they are, it is entirely conceivable for traffic to be diddled in arbitrary ways in real time
mircea_popescu: so basically, my node sent to trb nodes, trb nodes have it in memory but it's not being broadcast past them.
mircea_popescu doesn't know what to think atm, maybe it's some weirdo bug in the trb ? maybe what the shit.
mircea_popescu: hey asciilifeform are the trb nodes isolated atm ?!
asciilifeform: i generally go to ml when i look for 'what happened in xxx month trb-wise'
asciilifeform: anyway 'compile trb' was never a mega-feat
mircea_popescu: asciilifeform girl says it actually compiled trb. SO THERE.
asciilifeform: and for that matter, trb.
asciilifeform: (on all 3 trb nodes under my flag)
asciilifeform: http://log.bitcoin-assets.com/?date=05-01-2016#1361049 << is this where we learn that nobody's mining off trb ?
asciilifeform: -connect to the current trb nodes and spray it in, leave'em to broadcast
mircea_popescu: cool, ima run up a node from that cluster including the known trb nodes specifically. if you want to get yours included davout or anyone else pm me an ip.
mircea_popescu: as such, it is conceivable that z-80 powered trb can actually drive into the ground 12nm process powered united-prbs.
mircea_popescu: incidentally, i've been thinking lots about your famous silicone whine. (ie, "trb can't exist until etching plant"). from a twu wuv perspective, what we actually need is an alternate technology. i am guessing that a) it will exist and b) whoever deploys it will be trb anyway.
mircea_popescu: anyone wanna be trb-gcc maintainer ?
mircea_popescu: this would technically create trb-gcc wouldn't it
mircea_popescu: ascii_rear one theory would be that he was going to trb it.
mircea_popescu: or maybe he was going to do the equivalent of the trb but for debian and well... couldn't have that.
mircea_popescu: http://log.bitcoin-assets.com/?date=28-12-2015#1355361 << quite. all this verbiage about how "oh lalala, if miners stop enforcing X fork they will be excluded" fails to account for the fact that unlike the various PRBs, TRB does NOT actually implement any of the soft forks. so no, they won't be "excluded". nobody will notice they stopped.
asciilifeform: does anybody else find it lulzy that there are actually 2 trb's ?
asciilifeform: ben_vulpes: i think pete_dushenski was trying to write a history of trb ?
asciilifeform: and many other trb folks, i imagine, could also find this useful
asciilifeform: ;;later tell pete_dushenski http://log.bitcoin-assets.com/?date=18-08-2014#799538 << iirc this is the earliest point of reference for proto-trb
mircea_popescu: <punkman> isn't verifyall equivalent to no checkpoints? << in trb yes. otherwise... complicated.
asciilifeform: mod6: i meant on trb www site
asciilifeform: trb needs a 'db in the usual, general sense' like it needs a gene sequencer.
mircea_popescu: this is the problem of having a trb in the first place : the temptation to assume it's sane is just too great.
mircea_popescu: <ben_vulpes> interesting to note the various timelines for replication of trb work <<< quite.
mircea_popescu: anyway, for pete_d and anyone else who might have encountered difficulty with trb or fears they might : it's actually rather painless. 1. you create an account on a server ; 2. you cd /home/account_name ; 3. you create a .wot directory (mkdir .wot) ; 4. you put the pubkeys of people you trust in there as name1.asc, name2.asc etc ; 5. you download the rotor script (curl deedbot.org/build-bitcoind-99997K.sh > build-bitco
mircea_popescu: prolly should exist on the main page of trb site, at that.
mircea_popescu: polimedi@polimedia.us [~/trb/rotor]#
mircea_popescu: as it is i put .wot in /trb/.wot but the .seals are still up one level ;/
asciilifeform did not write the build script on trb site
asciilifeform: trb www
asciilifeform: http://log.bitcoin-assets.com/?date=21-12-2015#1349611 << if pete_dushenski is interested in the trb affair, prolly best bang for his buck will be to learn ~why~ various things were done, rather than the agonizing particulars of ~how~
asciilifeform: 'cause it isn't specific to trb
asciilifeform: see what differs from trb site
mircea_popescu: so far the mirror list consists of trb site.
asciilifeform: trb site ?
asciilifeform: all 3 of my currently operating trb nodes are using a rotor-on-musl build
mircea_popescu: asciilifeform remind me, where's teh instructions for pressing a trb ?
asciilifeform: shinohai: trb node is already there, see thread
asciilifeform: ;;later tell VariaVarietatis please ask all trb questions in #bitcoin-assets
asciilifeform: gentlement, please welcome (back) bucephalus: 216.15.33.203:8333 - a trb node, now running asciilifeform's bleeding-edge (on musl-rotor)
mircea_popescu: Thinking in those terms, "Hey, TRB actually running on BSD as opposded to PRB sounds to me like it'd be huge, it must be made a point of public communication, I need datas to support me in discussing this with people, plox to help me here!" is a helluva lot more productive than "this is X's dominion". At the worst this will clarify that "nah, not really", at the best it'll help a lot of idiots understand why it nobody
asciilifeform: and everything that will ever come later in re: trb, will be vpatches on top of the contents of that cd.
asciilifeform: http://log.bitcoin-assets.com/?date=21-12-2015#1349020 << i'd like to actually press a cd. with the understanding that everything that will ever happen to the reference implementation, incl. compiler, asm, the whole toolchain shebang, all kernels worth looking at from the past, all trb dependencies, etc. WILL BE ON IT
mircea_popescu: <asciilifeform> incidentally the de-glibc-ized trb WILL run on netbsd now! << o hey!
asciilifeform: but notably, the result is NOT something that anybody will dive into and clean up trb-style
asciilifeform: i may have said this before, but it bears repeating - some folks might be labouring under unrealistic expectations re: what is possible with the reference trb.
asciilifeform: incidentally the de-glibc-ized trb WILL run on netbsd now!
asciilifeform: http://log.bitcoin-assets.com/?date=20-12-2015#1348397 << nah that thing is still up (though at the moment the only thing properly built there is a trb node)
asciilifeform is familiar but not in trbfoundation
asciilifeform: (an unsynced trb node is not good for much! because it rejects most tx)
asciilifeform: incidentally, gentlemen, please welcome (back) dulap! 46.166.165.30:8333 (nosuchlabs.com), a trb node running bleedingedge-asciilifeform+rotor(musl)
mircea_popescu: trb transactions will necessarily, always and everywhere be translatable to whatever shit-flavour-of-the-day "everyone" is using because "no reasonable objections".
asciilifeform: punkman: there was one, at one point i even cleaned it up a bit and posted to trb ml. BUT i was never actually able to get it to work
asciilifeform: a trb node in the 'blackhole' state is also extremely slow to respond to local api reqs
asciilifeform: incidentally, the latter habitually connects via ~my~ trb nodez
asciilifeform: incidentally, anybody ever succeed in getting a ~heap dump~ of a running trb ?
asciilifeform: (fragging in trb)
asciilifeform: anyone else operating trb within the reich seeing same ?
asciilifeform observes that his trb nodes have been 10-20 blx steadily behind latest-known, for at least a week
asciilifeform: http://log.bitcoin-assets.com/?date=05-11-2015#1317131 << might want to patch trb's version thing instead
mircea_popescu: "you can fuck up at most once per trb release"
mircea_popescu: maybe the managers were like "hey, b-a luminary and trb maintainer mod seeks is coming over, EVERYONE ON ATTENTION!!1. Joe, call your wife, I know we said we'd never put her on but man... THIS IS TMSR!"
mircea_popescu: you know it's a trivial fix for trb also.
mircea_popescu: ok ns copied from trb.org
mircea_popescu: we had some trbl yest.
← |
Random(trilema) | Download hourly DB snapshot | Get Source Code