log☇︎
3225 entries in 1.139s
asciilifeform: (and if it takes 100 hours to build motherfucking trb, it is NOT a workstation!)
assbot: Logged on 29-01-2016 18:58:55; ascii_butugychag: the overall idea i am trying to teach is that anybody changing a line of trb ought to be mindful of the work this creates for others
assbot: Logged on 29-01-2016 23:34:09; phf: http://glyf.org/tmp/trb-transition-hunks.png same as before but with a separate edge per hunk
assbot: Logged on 29-01-2016 22:09:55; phf: asciilifeform: check it http://glyf.org/tmp/trb-transition.png
assbot: Logged on 30-01-2016 01:42:16; punkman: does the trb server have room for a buildatron that eats patches and craps out bitcoind's?
assbot: Logged on 30-01-2016 01:42:16; punkman: does the trb server have room for a buildatron that eats patches and craps out bitcoind's?
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 ?
assbot: Logged on 29-01-2016 23:34:09; phf: http://glyf.org/tmp/trb-transition-hunks.png same as before but with a separate edge per hunk
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
assbot: Logged on 29-01-2016 23:34:09; phf: http://glyf.org/tmp/trb-transition-hunks.png same as before but with a separate edge per hunk
mircea_popescu: mod6 : latest trb v99996 on 91.218.246.31 says "blocks" : 4500, "connections" : 13,
punkman: does the trb server have room for a buildatron that eats patches and craps out bitcoind's? ☟︎☟︎☟︎
phf: and the one ascii requested, transition graph for when there's only one hunk per patch file http://glyf.org/tmp/trb-transition-hunks-asplode.png (i filtered out all the genesis files that don't have further transitions)
phf: http://glyf.org/tmp/trb-transition-hunks.png same as before but with a separate edge per hunk ☟︎☟︎☟︎
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 ?
phf: asciilifeform: check it http://glyf.org/tmp/trb-transition.png ☟︎
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.
ascii_butugychag: the overall idea i am trying to teach is that anybody changing a line of trb ought to be mindful of the work this creates for others ☟︎
BingoBoingo: ascii_butugychag: I guess I got to now. Shiva represents first serious mega-weaponized divergence of trb from prb
phf: is the approach to spin up thread/socket on trb side? current "telnet" could be extended to swank protocol
ascii_butugychag: adlai: i implanted a scheme runtime in a trb.
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 !
assbot: Logged on 29-01-2016 07:42:24; polarbeard: I've timestamped and categorized trb log lines, as well as improved the messages and removed (seeming never activated) destructive log rotation, here is the signed patch: https://gist.github.com/polarbeard/961aa315c69b89d2e613 in case somebody with a decent reputation wants to review it so I can submit it to the ml
assbot: Logged on 29-01-2016 07:42:24; polarbeard: I've timestamped and categorized trb log lines, as well as improved the messages and removed (seeming never activated) destructive log rotation, here is the signed patch: https://gist.github.com/polarbeard/961aa315c69b89d2e613 in case somebody with a decent reputation wants to review it so I can submit it to the ml
punkman: that said, I'm not sure any trb users will actually want to filter on <priority>
polarbeard: I've timestamped and categorized trb log lines, as well as improved the messages and removed (seeming never activated) destructive log rotation, here is the signed patch: https://gist.github.com/polarbeard/961aa315c69b89d2e613 in case somebody with a decent reputation wants to review it so I can submit it to the ml ☟︎☟︎
asciilifeform: for trb?!
mod6: im thinking that i'm gonna tag the release, and publish the release patch soon. just hoping that if any of it touches trb, that it'll be post-release patch so there are no conflicts.
mod6: does any of it touch any of trb's files?
ascii_butugychag: PeterL: the goal is much more modest, i just need something that lets me poke around a running 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)
polarbeard: all I can say is that log rotation is daily business on most decent systems, but if anybody has a rational answer against it I would not remove shitty-ghost-rotation from trb
asciilifeform: anything you say in 'private' about trb will generally end up having to be repeated at least once.
assbot: Logged on 24-01-2016 19:02:54; ben_vulpes: http://log.bitcoin-assets.com/?date=24-01-2016#1384173 << do you mean 'the full orchestra' as advertised on trb ml?
ben_vulpes: http://log.bitcoin-assets.com/?date=24-01-2016#1384173 << do you mean 'the full orchestra' as advertised on trb ml? ☝︎☟︎
pete_dushenski: http://log.bitcoin-assets.com/?date=24-01-2016#1383805 << i saw 2+ gb just from a couple of failed trb build attempts. it was like 2.7 gigs iirc. "bitcoin is not for the poor (who can't afford hd space)" (tm) (r) ☝︎
asciilifeform: so you can meaningfully probe the living trb
assbot: Logged on 24-01-2016 02:36:26; asciilifeform: tinyscheme welded onto trb
asciilifeform: polarbeard: based on trb.
asciilifeform: in trb.
asciilifeform: tinyscheme welded onto trb ☟︎
assbot: Logged on 22-01-2016 16:56:17; PeterL: does trb debug.log grow infinitely?
asciilifeform: it is bad enough that trb has 500 man-year of study baked into it. let's now add a 501st ?
assbot: Logged on 23-01-2016 05:20:23; 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.
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. ☝︎☟︎
polarbeard: I wanted to instrumentalize trb a bit, btw
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 ?
polarbeard: I've been toying with trb's building scripts, and I've managed to do a whole build, including sig verification and pressing by generating a makefile
thestringpuller: I want to see where the "churn" is in TRB.
ascii_butugychag: i suppose the theory is that we are morons, and will conclude that 'trb is broken, can't sync' ?
mircea_popescu: trinque i suspect this is what drove alf's ideas of you know, deliberate sabotage against trb nodes.
trinque: because his new trb node is at 152k
PeterL: does trb debug.log grow infinitely? ☟︎
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.
assbot: An historical timeline of The Real Bitcoin (TRB) development, part ii. | Contravex: A blog by Pete Dushenski ... ( http://bit.ly/1RXE2uA )
ben_vulpes: http://www.contravex.com/2016/01/21/an-historical-timeline-of-the-real-bitcoin-trb-development-part-ii/ << seconded for an in-depth discussion of the static build crapocalypse, and why we even bother with static builds anyways at the very least
trinque: thestringpuller │ trinque: y u no use trb? << it's in the works.
thestringpuller: trinque: y u no use trb?
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.
pete_dushenski: asciilifeform: i can definitely say that the trb history is adding to ~my~ confusion, but i don't see that as something to be avoided. my hope is that i'll eventually make enough sense of this to relay it concisely to others. still much work to do, no doubt.
assbot: An historical timeline of The Real Bitcoin (TRB) development, part ii. | Contravex: A blog by Pete Dushenski ... ( http://bit.ly/1JmEa3H )
asciilifeform: pete_dushenski: http://www.contravex.com/2016/01/21/an-historical-timeline-of-the-real-bitcoin-trb-development-part-ii/#comment-39387
pete_dushenski: ;;later tell ben_vulpes you'll be pleased to find your trb history prominently linked in part ii :)
assbot: An historical timeline of The Real Bitcoin (TRB) development, part ii. | Contravex: A blog by Pete Dushenski ... ( http://bit.ly/1PrH83l )
pete_dushenski: asciilifeform: http://www.contravex.com/2016/01/21/an-historical-timeline-of-the-real-bitcoin-trb-development-part-ii/#comment-39384
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.
assbot: Logged on 21-01-2016 23:26:12; deedbot-: [Contravex: A blog by Pete Dushenski » Contravex: A blog by Pete Dushenski] An historical timeline of The Real Bitcoin (TRB) development, part ii. - http://www.contravex.com/2016/01/21/an-historical-timeline-of-the-real-bitcoin-trb-development-part-ii/
deedbot-: [Contravex: A blog by Pete Dushenski » Contravex: A blog by Pete Dushenski] An historical timeline of The Real Bitcoin (TRB) development, part ii. - http://www.contravex.com/2016/01/21/an-historical-timeline-of-the-real-bitcoin-trb-development-part-ii/ ☟︎
thestringpuller: TRB gives me hope
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: 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.
assbot: Successfully updated the rating for mod6 from 4 to 5 with note: His curative TRB leadership is a shining beacon for the entire Republic.
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
mod6: else { char *classic = "trb"; }
mircea_popescu: heh. the imf has no trb mandate, nor will it.
ascii_butugychag: unrelatedly, a crapple pad and one of the apps offered for that machine actually make an ok trb reader
pete_dushenski: ascii_butugychag: what ports can i use for trb while syncing ? and is there a good reason why trb should jump on 8333 without me telling it to, and without being completely synced ? because this seems to be a recurring issue on my end.
thestringpuller: looks like trb will have gossipd support?
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 ☟︎
assbot: Logged on 19-01-2016 23:48:49; punkman: I have a suggestion for an irc-bootstrap replacement in TRB. UDP torrent tracker announce, only takes a couple UDP packets, code's pretty simple. Recent client was using this in a small app, kinda cool.
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. ☝︎
assbot: Logged on 19-01-2016 23:48:49; punkman: I have a suggestion for an irc-bootstrap replacement in TRB. UDP torrent tracker announce, only takes a couple UDP packets, code's pretty simple. Recent client was using this in a small app, kinda cool.
punkman: I have a suggestion for an irc-bootstrap replacement in TRB. UDP torrent tracker announce, only takes a couple UDP packets, code's pretty simple. Recent client was using this in a small app, kinda cool. ☟︎☟︎
ascii_butugychag: mircea_popescu: yeah but in trb that 25MB goes with 500MB of frag gap
ascii_butugychag: mircea_popescu: trb mempool is 25MB perhaps... up to five minutes after warmup ?
ascii_butugychag: the solution to overloaded and shitflooded trb nodes is... to have 1000x more of'em
assbot: Logged on 18-01-2016 15:15:10; mod6: Attention TRB Testers: If you want to help test, please take the time to build trb via trinque's makefiles here; http://therealbitcoin.org/ml/btc-dev/2016-January/000190.html (Should be basically getting & verifing the tar ball; plus setting up a ~/.wot dir with keys for V to use) -- then a `make` in the directory. Please report your findings. Thanks.