3 ms·

That's giving too much credit. His predictions were incorrect, and not by a small amount. I'm no Bitcoin developer, but a month ago it was obvious to me that Se

by ggreer 11y ago

That's giving too much credit. His predictions were incorrect, and not by a small amount. I'm no Bitcoin developer, but a month ago it was obvious to me that Segregated Witness would require far more code than a block size increase. Maxwell thought SegWit would be smaller, but even its current (incomplete) state is bigger by a factor of four. That's not a small mistake. It indicates a fundamental misunderstanding somewhere along the line. The more I read comments made by Core devs, the more I think they are either mistaken or misleading. I truly wish this wasn't the case. Lastly, I hope this back-and-forth has given you a better grasp of the subject and caused you to change your mind on some things. I can't shake the idea that you're trying to convince others rather than figure out what's true. And judging from recent comments on HN, you seem to be overconfident in your technical abilities (not knowing how to use GitHub, thinking HTTPS is too resource-intensive for many applications, etc). I urge you to be more self-critical in the future.

ikeboy 11y ago
The difference wasn't that segwit got bigger, it was that the other patch got smaller. (Or rather, looking at it again, he's referring to BIP101 which was an adjustable size HF). I don't see why not knowing how to check the line difference in github implies a lack of technical skill. The claim about https I had taken directly from a site which claimed they didn't host it on https because it was too expensive. I haven't dealt directly with testing https on a large scale, but again, that's hardly a core technical skill, except for someone running webservices. I've changed to a bit more uncertainty on the difference between soft forks and hard forks based on someone else's comments here. I'm not sure if I've changed my mind on anything due to your comments in particular (except that the classic fork is indeed smaller). I'm not sure what I can do about incorrect information from an unreliable source that I'm not aware is incorrect. Do you have any practical piece of advice on that besides "be more self-critical"? (Because the practical consequence of such self-criticalness would be less posting on subjects I'm semi-confident about, and while I'm occasionally wrong, I think I'm overall contributing in a beneficial way. I wouldn't have >2500 karma here if I wasn't.)

by ggreer 11y ago

ikeboy 11y ago

The difference wasn't that segwit got bigger, it was that the other patch got smaller. (Or rather, looking at it again, he's referring to BIP101 which was an adjustable size HF). I don't see why not knowing how to check the line difference in github implies a lack of technical skill. The claim about https I had taken directly from a site which claimed they didn't host it on https because it was too expensive. I haven't dealt directly with testing https on a large scale, but again, that's hardly a core technical skill, except for someone running webservices. I've changed to a bit more uncertainty on the difference between soft forks and hard forks based on someone else's comments here. I'm not sure if I've changed my mind on anything due to your comments in particular (except that the classic fork is indeed smaller). I'm not sure what I can do about incorrect information from an unreliable source that I'm not aware is incorrect. Do you have any practical piece of advice on that besides "be more self-critical"? (Because the practical consequence of such self-criticalness would be less posting on subjects I'm semi-confident about, and while I'm occasionally wrong, I think I'm overall contributing in a beneficial way. I wouldn't have >2500 karma here if I wasn't.)