log☇︎
141600+ entries in 1.137s
punkman: trinque: I think that's to be expected with orphanage amputations. I have those and also plenty of "ERROR: AcceptToMemoryPool() : nonstandard transaction type"
trinque: yeah, I'm being hyperbolic ☟︎☟︎
williamdunne: I'm not going to disagree with you completely, but I do still believe that S&P500 beats inflation by a couple of percent
trinque: I'm sure they used to mean something else, but we're in bizarro land where the length of a meter changes day to day
trinque: williamdunne: I tend to take stock market prices as inflation indicators these days
trinque: I am seeing a bunch of ERROR: AcceptToMemoryPool() in my stator run
asciilifeform: (not a connectivity problem - i'm getting mempoolisms just fine)
asciilifeform: mod6: i've been synced for ~1hour and it looks like it's firmly stuck there
mod6: <+phf> apparently gcc doesn't always include all the necessary pthread bits (not just openbsd but other unixes), which results in segfault on launch << on my obsd 5.6 on x86-64 that's the same problem i kept running into; segfault at execution time.
punkman: heh "I shook hands with the man I did most of the talking with and they took off... I was a little shooken up but realized I made a big mistake! I forgot to shake the black police detective's hand... shit!!! "
asciilifeform: ;;later tell mircea_popescu i built stator on dulap just now. unchanged from public recipe other than the 'realpath' thing (mentioned earlier.) same process ought to work on your other centos boxes. it will run as a public node as soon as i shove a blockchain in there.
phf: asciilifeform: i have a small backlog of things i want to send to the list, i'll wrap it up sometime over the weekend
punkman: 30k student email list? I scraped like 5mil for leet sv startup last year. ☟︎
phf: i had to make some minor changes http://paste.lisp.org/display/151074
asciilifeform: 'nd that they sell over 30k student emails for $20, which I had bought;' << l337 sp4mz0r ?
punkman: yeah that's what I did
asciilifeform: i did learn that many linux distros lack 'realpath' ☟︎
punkman: no-verifysig-skipping stator reached 169k, so I'm gonnna call this a success for now.
shinohai: congrats, I am still about 167k or so
asciilifeform: ... and now i'm synced with mircea_popescu.
cazalla: now and then i've thought of the few teacher's aids that would come for a school term as part of their studies.. they were so young and pretty but would be old bags now
shinohai: I always wanted to fuck my math teacher. She was smokin'
cazalla: tbh at 17 i think i would've been willing to do 22 years to fuck my english teacher
kakobrekla: or should i say only not-earth
mircea_popescu: i thought reddit went private.
mircea_popescu: honestly i fully expect fail to "happen"
punkman: petertodd: "Honestly I was half-expecting this to happen, and was actually busy writing up a warning for SPV wallets users when this issue came up."
shinohai: I'm at 254300 this morning, yay
kakobrekla: http://log.bitcoin-assets.com/?date=04-07-2015#1186613 < i dont see any difference? ☝︎
punkman: I just started a stator patched to not skip VerifySignature, wonder if it'll work this time
mircea_popescu: "dude i could have been so rich and important".
midnightmagic: Dude wears the Halo. The other scammers don't matter so much. And if I really cared, I'd be doing something other than flicking out belly button lint in the shower. I'm just curious to know why *you guys* stopped.
mircea_popescu: i think what ? how is this even a problem ?
assbot: Logged on 04-07-2015 06:24:27; midnightmagic: Unless you are implying people outside the bitcoin world are voracious readers of the -ass logs, as far as I can tell in all the articles, reddit posts, twitter feeds, etc, I don't see more than a passing mention. But even if that weren't so, really I'm a little disappointed the wind all went out of your sails, as it were.
assbot: Logged on 04-07-2015 06:18:37; midnightmagic: it's all a question of how much you trust your ability to make code that converges on consensus. are you so awesome you can either sit on an old openssl, or write your own replacements? are you so godlike you can write testcases for every corner-case, bugs and all? I know I'm not. Maybe you guys are. I dunno.
assbot: Logged on 04-07-2015 06:14:44; midnightmagic: because, like I said, I think some people in there appear to be adding exploitable code with absurd frequency.
midnightmagic: No, but I do know for a fact that procrastination has saved my life at least six or seven times. :)
midnightmagic: I meant to suggest that the amount of effort of doing it oneself compared with the projected risk of it happening while someone else is working on it.. which option is less expensive/reliable?
assbot: Logged on 04-07-2015 06:11:21; midnightmagic: well, then we have the forking risk I mentioned above: what happens when the openssl people make a fix or the internet finds a bug in the component that we depend on? If we sit on 0.9.8 or whatever the version was before those idiots got their hands on it and started adding malicious exploits, what happens?
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186847 << while this problem exists, i think the case that it is strictly preferable to attempt building a functional system than to bemoan one's fate of having been born to parents this poor, stupid and useless needs not be further pressed. ☝︎
assbot: Logged on 04-07-2015 06:06:14; midnightmagic: I'm familiar with the DER-encoding change they made, and I'm aware of, if not familiar with, every major bug in openssl since 2001 or so. Could I draw a line between releases that had bugs and releases that fixed them? No. Not even close.
mircea_popescu: i mean, other than painting the picture of the vermin in unflattering tones, which it does. in the field it can do precisely jack.
assbot: Logged on 04-07-2015 05:26:45; decimation: I would also note that the bitcoind github commits and comments lie about the IsSuperMajority machine. They say that the mandatory rejection won't take effect until 95% of the blocks are incremented - but in fact it's only 950
mircea_popescu: i believe the lesson was learned.
assbot: Logged on 04-07-2015 04:47:46; decimation: I would say that on its face, bip66 isn't such a terrible idea
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186697 << i dun think it does anything useful ; on the other hand it doesn't do anything whatsoever that wasn't either already done, or as good as already done. but whatever, let the flies buzzing in front of the truck get their fly trophies for opening the road to trucks. ☝︎
assbot: Logged on 04-07-2015 02:46:46; asciilifeform: what i think would be considerably more useful is a provision for 'programmable checkpoints'
assbot: Logged on 04-07-2015 02:07:07; DanyAlos: I was looking for #bitcoin-assets on this search engine (http://irc.netsplit.de/channels), and realized that it is not listed. Is there any particular reason for not being there?
decimation: at any rate, I'm going to sleep, I'm sure others will comment tomorrow on this discussion.
decimation: I think there's a general ambivalence about what bitcoin-devs want or do
midnightmagic: Yes, I saw all that. I mean *outwardly* quiet.
thestringpuller: midnightmagic: cause I fucked up my shoulder being on the computer all day at work so I read comic books instead after work.
ben_vulpes: i thought you said you were reading logs!?
midnightmagic: thestringpuller: not at all, I mainly wanted to know why you all were being so quiet lately. :-P
thestringpuller: oh did i come back for drama?
ben_vulpes: <midnightmagic> ben_vulpes: Dude man, with the shit you guys say in here, I have no idea when you're ribbing someone, or promising a spear in the gut. :( << the ambiguity has to be completely intolerable
midnightmagic: ben_vulpes: Dude man, with the shit you guys say in here, I have no idea when you're ribbing someone, or promising a spear in the gut. :(
midnightmagic: I grok.
decimation: all I can say, for myself, is that folks write stuff on this channel, I would read; comment - as would others
midnightmagic: I guess that answers my question.
decimation: umm, why would we give a shit about what they are saying otherwise? I donno bro, you're the one accusing here.
trinque: gonna let this run for a while, then I'll share the results
midnightmagic: I presumed your head would explode if I mentioned forbes (due to its primary bitcoin author being a douchebag), or mainstream media.
decimation: I don't really read reddit or twitter, but I recall that gavin captiulated, more or less
midnightmagic: Unless you are implying people outside the bitcoin world are voracious readers of the -ass logs, as far as I can tell in all the articles, reddit posts, twitter feeds, etc, I don't see more than a passing mention. But even if that weren't so, really I'm a little disappointed the wind all went out of your sails, as it were. ☟︎
ben_vulpes: <midnightmagic> Yeah, I mean aside from the grumbling in here which nobody but people *in here* seems to read. << how could you possible know
midnightmagic: Yeah, I mean aside from the grumbling in here which nobody but people *in here* seems to read.
midnightmagic: it's all a question of how much you trust your ability to make code that converges on consensus. are you so awesome you can either sit on an old openssl, or write your own replacements? are you so godlike you can write testcases for every corner-case, bugs and all? I know I'm not. Maybe you guys are. I dunno. ☟︎
decimation: his code sucks, I don't deny, but it's the closest thing to a spec that we have
ben_vulpes: it's all well and good to say "strip out the components", i just don't buy that that's possible.
midnightmagic: because, like I said, I think some people in there appear to be adding exploitable code with absurd frequency. ☟︎
midnightmagic: I'm not pretending that; I'm explicitly saying, divergence implies there is no reason to even *use* openssl at that point. strip out the components, use them, skip openssl entirely, and, I guess, trust in your ability to monitor the progenitor of your codebase for bugs that *explicitly affect your consensus-critical code*.
midnightmagic: ben_vulpes: You can keep guessing what I mean without actually asking me, but you're no less wrong.
midnightmagic: well, then we have the forking risk I mentioned above: what happens when the openssl people make a fix or the internet finds a bug in the component that we depend on? If we sit on 0.9.8 or whatever the version was before those idiots got their hands on it and started adding malicious exploits, what happens? ☟︎
midnightmagic: lol. No, it's not news to me. Yes, I already knew that.
ben_vulpes: this, i gather, is news to you.
midnightmagic: I'm familiar with the DER-encoding change they made, and I'm aware of, if not familiar with, every major bug in openssl since 2001 or so. Could I draw a line between releases that had bugs and releases that fixed them? No. Not even close. ☟︎
midnightmagic: ben_vulpes: On that at least, we agree. I agree with that: the current hashrate is as illegitimate as a vote of private keys would be in determining a softfork. What else is there?
midnightmagic: Correct. I am saying your complaint about it being unreasonable is illogical by any measure of the mining work done: there *is* no other meaningful window, or measurement, of the bitcoin network without shifting to PoS or DPoS. But if you want to do that, fork bitshares.
ben_vulpes: i don't accept it either.
decimation: I don't accept it.
decimation: I think it's likely to level out in the coming year or two, maybe longer
midnightmagic: i'm just saying that it sounds like a little bit in comparison to both time, and integerial block height, but actual work-wise it a significant chunk. again, very unfortunately.
decimation: I would also note that the bitcoind github commits and comments lie about the IsSuperMajority machine. They say that the mandatory rejection won't take effect until 95% of the blocks are incremented - but in fact it's only 950 ☟︎
mod6: i put it out there on derp-media too
decimation: I'm fairly certain that if 0.5.3.1 were used to mine a block with nVerion=1 it would be rejected
trinque: ben_vulpes: guess what else I'll be rewriting in cl at some point.
mod6: yeah, i should have just pointed him to your blog.
ben_vulpes: "reasons" being that i wrote a blog post saying "i don't think much happened after this"
mod6: anyway, you think i should have just called him out instead of saying "reasons"?
mod6: <+ben_vulpes> << this still hurts, every time i see it << awe!
ben_vulpes: http://log.bitcoin-assets.com/?date=21-01-2015#985356 << this still hurts, every time i see it ☝︎
decimation: http://log.bitcoin-assets.com/?date=21-01-2015#985338 < I think this is what he was talking about (nVersion) ☝︎
ben_vulpes: an informal signoff from y'bosses would be nice before i deposit this in the white porcelain turdotron
decimation: asciilifeform: I can already hear jwz saying that he doesn't want politics, just to do the right thing
decimation: although as I've noted, they already incremented this machine
decimation: I would say that on its face, bip66 isn't such a terrible idea ☟︎
ben_vulpes: mircea_popescu, mod6, asciilifeform: i don't see a reason to make this much more than 25 words. do you think much detail or polemic is necessary here?
ben_vulpes: ugh man i kinda hate this
ben_vulpes: i'm nominally on vaycay but...panzer