log☇︎
3225 entries in 1.062s
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
danielpbarron: i have a trb node that is not yet full, currently at block 312275
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.
punkman: CVE-2012-2459 isn't though, maybe a good thing to fix next trb release
mircea_ahoy: nobody's actually involved in making bitcoin not suck. there's a large group of idiots involved in trying to make themselves look good, and there's trb trying to make bitcoin be less g narly.
mircea_ahoy: are you using trb or bullshit-b ?
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.
pete_dushenski: ascii_rear: btw can you please explain http://therealbitcoin.org/ml/btc-dev/2015-April/000080.html to me for the purposes of part ii of the trb history series ?
pete_dushenski: much credit is due to the whole trb team for developing the package as we enjoy it today
BingoBoingo: So you goes your trb adventure?
BingoBoingo: No matter how much hair is lost to polishing trb, let us all be thankful trb will nevar have these solutions: https://archive.is/a48Ko
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.
shinohai: o/ pete_dushenski enjoy your trb node!
adlai: damnit mod6, isn't that a fiat thing? someday trb should fix the calendar, too
assbot: Logged on 22-12-2015 04:58:44; 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-9999
adlai: brb bullshitting it off trb financial statements
mircea_popescu: or maybe he was going to do the equivalent of the trb but for debian and well... couldn't have that.
pete_dushenski: *cough* trb *cough*
assbot: Successfully added a rating of 1 for ben_vulpes with note: Bash necromancer of trb things. http://cascadianhacker.com
shinohai: !rate ben_vulpes 1 Bash necromancer of trb things. http://cascadianhacker.com
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. ☝︎☟︎
assbot: Successfully added a rating of 1 for shinohai with note: trb scout
ben_vulpes: !rate shinohai 1 trb scout
pete_dushenski: mnope. that one has a larger breadth than contravex trb timleline part i could handle. maybe in part ii.
asciilifeform: does anybody else find it lulzy that there are actually 2 trb's ?
pete_dushenski: 1.25 years of development of trb is equivalent to multiples of that in row
asciilifeform: ben_vulpes: i think pete_dushenski was trying to write a history of trb ?
ben_vulpes: and yet somehow trb forked from 0.5.3
pete_dushenski: ;;later tell mod6 my pleasure and thanks for the correction. i was confusing december 19th entries, it seems. i've updated that section of the trb timeline accordingly.
ben_vulpes: and miscellaneous other pasteshites who shit crlfs and waste precious trb time
ben_vulpes: that's what i've been doing, but it's not working and i'm still seeing heinous linefeed issues hamstringing and tripping up trb scouts
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.
deedbot-: [Contravex: A blog by Pete Dushenski » Contravex: A blog by Pete Dushenski] An historical timeline of The Real Bitcoin (TRB) development, part i. - http://www.contravex.com/2015/12/25/an-historical-timeline-of-the-real-bitcoin-trb-development-part-i/
asciilifeform: mod6: i meant on trb www site
asciilifeform: trb needs a 'db in the usual, general sense' like it needs a gene sequencer.
ben_vulpes: why the everloving fuck would trb care about rtrees
ben_vulpes: http://log.bitcoin-assets.com/?date=24-12-2015#1351774 << conversation wasn't strictly about trb but dbs in general ☝︎
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.
shinohai: qt is just a bloated monstrosity. I love trb even more because it lacks any part of it.
ascii_field: http://blog.llvm.org/2013/04/status-of-c11-migrator.html << possible useful tool for boost removal in trb
assbot: Logged on 22-12-2015 06:37:41; ben_vulpes: interesting to note the various timelines for replication of trb work
mircea_popescu: <ben_vulpes> interesting to note the various timelines for replication of trb work <<< quite.
ben_vulpes: interesting to note the various timelines for replication of trb work ☟︎
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.
mod6: <+mircea_popescu> as it is i put .wot in /trb/.wot but the .seals are still up one level ;/ << noted.
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 ;/
assbot: Logged on 21-12-2015 22:53:29; 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 did not write the build script on trb site
asciilifeform: trb www
assbot: Logged on 21-12-2015 21:21:34; pete_dushenski: mircea_popescu: but your controlling point about whose dominion is a thing is well taken. the boundaries here are very loosely defined, and yet so broad that i'm bound to miss important things, but mostly as these important things relate to trb development, an area where my only experience was debian testing and v-verification this summer
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
assbot: Logged on 21-12-2015 21:24:59; mircea_popescu: asciilifeform remind me, where's teh instructions for pressing a trb ?
pete_dushenski: this set of newly delivered readings is just some of the competition for my time that retards my learnings of trb and related subjects
mircea_popescu: asciilifeform remind me, where's teh instructions for pressing a trb ? ☟︎
pete_dushenski: mircea_popescu: but your controlling point about whose dominion is a thing is well taken. the boundaries here are very loosely defined, and yet so broad that i'm bound to miss important things, but mostly as these important things relate to trb development, an area where my only experience was debian testing and v-verification this summer ☟︎
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)
BingoBoingo: But the alf experiment of see how many nodes trb needs before being censored is worth at least two chuckles
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
assbot: Logged on 21-12-2015 06:25:36; pete_dushenski: besides, is not trb news the dominion of mod6 'state of bitcoin addresses' or qntra ? i can certainly qntra, but i guess i'm not equipped to appreciate the significance of glibc-less-netbsd
BingoBoingo: pete_dushenski: As penance you should fire up a trb node to test the new version string patch
pete_dushenski: and thank god it's only part of b-a because the trb-dev stuff is waywaywayway over my head
pete_dushenski: b-a is ground zero for trb-dev
BingoBoingo: sure trb progress
pete_dushenski: this being the trb progress ?
pete_dushenski: sorry, trb sans glibc on netbsd, to be more precise
pete_dushenski: besides, is not trb news the dominion of mod6 'state of bitcoin addresses' or qntra ? i can certainly qntra, but i guess i'm not equipped to appreciate the significance of glibc-less-netbsd ☟︎
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 ☝︎
assbot: Logged on 21-12-2015 00:03:55; mircea_popescu: <asciilifeform> incidentally the de-glibc-ized trb WILL run on netbsd now! << o hey!
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
assbot: Logged on 20-12-2015 22:01:59; asciilifeform: incidentally the de-glibc-ized trb WILL run on netbsd now!
shinohai: http://log.bitcoin-assets.com/?date=20-12-2015#1348925 /me has been unsuccessful building trb on any bsd as of yet ☝︎
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.
mod6: or simply just a manifest of tarballs/deps required for the one-button-push deployment of trb
asciilifeform: incidentally the de-glibc-ized trb WILL run on netbsd now! ☟︎
assbot: Logged on 20-12-2015 00:17:11; asciilifeform: incidentally, gentlemen, please welcome (back) dulap! 46.166.165.30:8333 (nosuchlabs.com), a trb node running bleedingedge-asciilifeform+rotor(musl)
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: (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
ben_vulpes: a trb node doing much of anything at all is pretty slow to respond to local api requests.
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