Pages:
Author

Topic: Stop fuckin' around, fork the son-of-a-bitch already. (Read 9352 times)

legendary
Activity: 1596
Merit: 1026
Hard forks are good.  Stop crying.  They allow two discrete paths to flourish and see which works best.  Too freaking bad if some of your juice gets stuck on the 'bad' chain.  On fork day, you've got equal action on both chains.  Make good decisions thereafter.  No harm, no foul.  

Let's do it NOW!!!!

Fork it already.
Who`s crying?I don`t understand.
Folks are saying a hard fork is 'dangerous'.  It is only dangerous for the undesirable prong. 
hero member
Activity: 3150
Merit: 937
Hard forks are good.  Stop crying.  They allow two discrete paths to flourish and see which works best.  Too freaking bad if some of your juice gets stuck on the 'bad' chain.  On fork day, you've got equal action on both chains.  Make good decisions thereafter.  No harm, no foul.  

Let's do it NOW!!!!

Fork it already.

Who`s crying?I don`t understand.

Are there people who complain about the hard fork?

What`s the point of this thread?
legendary
Activity: 1596
Merit: 1026
the current ACTUAL debate is consensual '2base-4mbweight' buffer increase by EVERYONE in the community releasing an implementation. so that fans of any implementation can all happily stick with their favourites and still have the open choice to decentrally vote in or out of a safe increase of capacity, while not hindering segwit either, or having to change to another "brand"
yes this means the quadratics doomsday is also a moot point because segwit still gets to work
I honestly have read this post three times by now, and still fail to understand what you've wanted to say with it. Not because of "technicalities", but because the flawed construct of all those sentences. You should really rephrase everything.
in short
core releasing 0.13.2a with 1base 4weight AND releasing 0.13.2b with 2base 4weight

that way core fanboys dont have to defect away from core to get real capacity, they can choose freely while remaining with core dream team
that way the community as a whole have an open choice without having any bias
that way you can finally be happy of your dream team having code for all the features the community have been requesting.
that way you can chill out your doomsdays because core is no longer vetoing the 2mb base option, to cause controversy

now with change of guard at Blockstream, maybe the pro fork people can get a little more momentum going and
'get 'er done'
legendary
Activity: 4410
Merit: 4766
the current ACTUAL debate is consensual '2base-4mbweight' buffer increase by EVERYONE in the community releasing an implementation. so that fans of any implementation can all happily stick with their favourites and still have the open choice to decentrally vote in or out of a safe increase of capacity, while not hindering segwit either, or having to change to another "brand"
yes this means the quadratics doomsday is also a moot point because segwit still gets to work
I honestly have read this post three times by now, and still fail to understand what you've wanted to say with it. Not because of "technicalities", but because the flawed construct of all those sentences. You should really rephrase everything.
in short
core releasing 0.13.2a with 1base 4weight AND releasing 0.13.2b with 2base 4weight

that way core fanboys dont have to defect away from core to get real capacity, they can choose freely while remaining with core dream team
that way the community as a whole have an open choice without having any bias
that way you can finally be happy of your dream team having code for all the features the community have been requesting.
that way you can chill out your doomsdays because core is no longer vetoing the 2mb base option, to cause controversy
legendary
Activity: 2674
Merit: 2965
Terminated.
the current ACTUAL debate is consensual '2base-4mbweight' buffer increase by EVERYONE in the community releasing an implementation. so that fans of any implementation can all happily stick with their favourites and still have the open choice to decentrally vote in or out of a safe increase of capacity, while not hindering segwit either, or having to change to another "brand"
yes this means the quadratics doomsday is also a moot point because segwit still gets to work
I honestly have read this post three times by now, and still fail to understand what you've wanted to say with it. Not because of "technicalities", but because the flawed construct of all those sentences. You should really rephrase everything.
legendary
Activity: 4410
Merit: 4766
the current ACTUAL debate is consensual '2base-4mbweight' buffer increase by EVERYONE in the community releasing an implementation. so that fans of any implementation can all happily stick with their favourites and still have the open choice to decentrally vote in or out of a safe increase of capacity, while not hindering segwit either, or having to change to another "brand"
yes this means the quadratics doomsday is also a moot point because segwit still gets to work
legendary
Activity: 2674
Merit: 2965
Terminated.
Yeah it's a privately owned forum, but it's the main forum for bitcoin, and it would be good for the benefit of all bitcoin users if this forum remained neutral.   
I disagree with your view of "main forum" here. It surely is the most used forum, however you aren't creating any arguments for your case actually. If users wanted a more "neutral" environment (whatever this is supposed to mean), they'd simply start using one. That's how these things usually work, nobody is forcing you to stay nor leave.

The fact that this forum is not neutral is very worrying, is this is already a first step in centralizing bitcoin.   
No, it's not worrying at all. Besides, this isn't the thread here. You should probably keep this consistent to the thread that you've made in Meta.

This should be about a potential fork (although we drifted away from time to time).
legendary
Activity: 1106
Merit: 1005
C++
explicit limit vs consensus limit
consensual vs controversial
reading code not social distraction
definition of hypocrisy
who is spoon-feeding him and why they do it
You've nicely described yourself. Focusing on ad hominem won't do you any good nor win any arguments.

The main forums (this one, and /r/bitcoin) both support Core as the only 'official' bitcoin wallet. Most users probably don't even know about Classic/Unlimited/XT, and if they do, they don't know they are just as 'official' as Core.    
It is the main and most advanced Bitcoin implementation. There's nothing "official" regarding that.

Basically, this header needs to be more neutral, and also include links to the latest Classic, Unlimited and XT clients. As well as a link to a page that explains the difference in a fair and factual way.      
No. This is a privately owned forum, and as such, does not "need" to do anything.

Yeah it's a privately owned forum, but it's the main forum for bitcoin, and it would be good for the benefit of all bitcoin users if this forum remained neutral.   

The fact that this forum is not neutral is very worrying, is this is already a first step in centralizing bitcoin.   

and then they claim Core is trying to keep bitcoin decentralized. What a joke.
legendary
Activity: 4410
Merit: 4766
seems someone preferred to avoid the topic to adhom about an adhom

now then.

the current ACTUAL debate is consensual '2base-4mbweight' buffer increase by EVERYONE in the community releasing an implementation. so that fans of any implementation can all happily stick with their favourites and still have the open choice to decentrally vote in or out of a safe increase of capacity, while not hindering segwit either, or having to change to another "brand"
yes this means the quadratics doomsday is also a moot point because segwit still gets to work
legendary
Activity: 2674
Merit: 2965
Terminated.
C++
explicit limit vs consensus limit
consensual vs controversial
reading code not social distraction
definition of hypocrisy
who is spoon-feeding him and why they do it
You've nicely described yourself. Focusing on ad hominem won't do you any good nor win any arguments.

The main forums (this one, and /r/bitcoin) both support Core as the only 'official' bitcoin wallet. Most users probably don't even know about Classic/Unlimited/XT, and if they do, they don't know they are just as 'official' as Core.    
It is the main and most advanced Bitcoin implementation. There's nothing "official" regarding that.

Basically, this header needs to be more neutral, and also include links to the latest Classic, Unlimited and XT clients. As well as a link to a page that explains the difference in a fair and factual way.      
No. This is a privately owned forum, and as such, does not "need" to do anything.
legendary
Activity: 1106
Merit: 1005
once you have researched what they all actually are.
-snip-
You yourself have no idea what they all actually are.

ive read the code of each. but find it funny that you dont know they all do the same basic function once you wash away the fluffy buzzwords.
you should have don yourself a favour last year and actually learned some C++ to actually actively engage in some real understanding of bitcoin.

but have a happy year with you subliminal mind programming set to:
BU=warewolves and Classic=vampire, kill kill kill.. core=king devote devote devote




I'm convinced most people support Core not because they actually think it's better, but because they don't know any better.

The main forums (this one, and /r/bitcoin) both support Core as the only 'official' bitcoin wallet. Most users probably don't even know about Classic/Unlimited/XT, and if they do, they don't know they are just as 'official' as Core.    

The thing about decentralization is, there isn't one official client. There are multiple.      

The 'official' client is the client that gets the most support from the users/miners/merchants/etc.      

I think it's wrong to have only Core being advertised on bitcointalk.org and /r/bitcoin. It gives the wrong impression and it's very centralized.      

Basically, this header needs to be more neutral, and also include links to the latest Classic, Unlimited and XT clients. As well as a link to a page that explains the difference in a fair and factual way.       

The way it is done now only leads to centralization of bitcoin.
legendary
Activity: 4410
Merit: 4766
things lauda needs to learn

C++
explicit limit vs consensus limit
consensual vs controversial
reading code not social distraction
definition of hypocrisy
who is spoon-feeding him and why they do it

now then.
the current ACTUAL debate is not laudas meandered hypocrisy of the doomsdays of controversial forks of 16mb by groups of warewolves and vampires preventing linear.

but consensual '2base-4mbweight' buffer increase by EVERYONE in the community releasing an implementation. so that fans of kings, warewolves and vampires can all happily stick with their favourites and still have the open choice to decentrally vote in or out of a safe increase of capacity which still allows the kings to have their way too, and no one thinking they have to jump camps to get it.
yes this means the quadratics doomsday is also a moot point because segwit still works
again it does not mean segwit wont function by increasing the 2mb base, so relax lauda your kings still have a job and are not sacked
again this does not mean any excess bloat that kings are not also accepting as safe
legendary
Activity: 2674
Merit: 2965
Terminated.
Does that make you honest? No - it makes you a liar that has been caught in a lie.
No. I was proving a point which you seem to have missed.

ive read the code of each.
What a nice joke. Roll Eyes

Based on that, it sounds like you're not even remotely educated on what these alternative implementations are or how they work.  
I'm "educated" enough about BU to not be interested in their work at this time. The reason that I used the "16 MB" was because somebody was advocating that 16 MB blocks were safe, which is obviously false.

You seemingly just regurgitate opinions you've read elsewhere without even bothering to check the legitimacy of it.
If that was the case, then I'd be supporting Bitcoin Classic and BU.

It's precisely the point.  
No. That was a demonstration of the assertions being throw out by pro-BU members around here.

Again with the garbage assumptions.  Perhaps you could explain why you're skeptical about the proposals and in the process prove that you actually understand them.  
You tell me to do research, and then afterwards want me to explain why e.g. header-first mining is a bad idea? How about you do the research this time?

Obviously we're long past any technical debate in this thread, and are at a point where the mindset being received is in the lines of "No, you're wrong. xx MB blocks are super safe. Core is evil".
legendary
Activity: 3948
Merit: 3191
Leave no FUD unchallenged
It has been tested on testnet already. Stop spreading misinformation. There's nothing dangerous about bigger blocks.
The BU testing methodology is garbage and should not be used as 'evidence' for anything.

In fairness, you would sound far more convincing if you actually did a bit of research and didn't spurt out things like:

Not to mention that if we moved to BU today (to their block size limit setting which I at a weird number; 16 MB I think?), the network would likely end up useless due to DOS attacks.

Based on that, it sounds like you're not even remotely educated on what these alternative implementations are or how they work.  You seemingly just regurgitate opinions you've read elsewhere without even bothering to check the legitimacy of it.


The problem is that these "other implementations" only have half-baked, horribly coded improvements.
Interesting assertion. I'd like to read your extensive code review of each such "other implementation".
There isn't an extensive code review of such an implementation by myself (probably not by anyone, as I haven't seen one). That's not the point though.

It's precisely the point.  You're slamming something you haven't even attempted to comprehend.  People are now falling over each other to point out that fact and you're making it very easy for them.


i think its time lauda goes spend a few hours to ask his friends the difference between xthin and headers first
Again, I have no "friends" to ask. Anyhow, both of those proposals are such garbage that looking into them is a waste of time.

Again with the garbage assumptions.  Perhaps you could explain why you're skeptical about the proposals and in the process prove that you actually understand them.  Or you could dismiss them as "garbage" and we'll all assume that you're just guessing again because you read something in passing and decided it must be true without questioning it.
legendary
Activity: 4410
Merit: 4766
once you have researched what they all actually are.
-snip-
You yourself have no idea what they all actually are.

ive read the code of each. but find it funny that you dont know they all do the same basic function once you wash away the fluffy buzzwords.
you should have don yourself a favour last year and actually learned some C++ to actually actively engage in some real understanding of bitcoin.

but have a happy year with you subliminal mind programming set to:
BU=warewolves and Classic=vampire, kill kill kill.. core=king devote devote devote


legendary
Activity: 1106
Merit: 1005


No one has the money to set up a several months long non-stop spam attack.
This got to be a bad joke, right? A fair amount of people have enough money to spam up the network for a very long time.



Right, I'm sorry.

Bill gates, would you please stop spamming the bitcoin? The Core team already caught up on it and they aren't falling for it.    


I haven't been following this thread, so excuse the question if it has already been asked and answered:

Setting aside areas of technical disagreement for a second, what are the issues/areas for which there is technical agreement?

1. 21M coins
2. What else?
3. etc. ?



Maybe 10 minute average block time.

But maybe some people disagree on that too.

hero member
Activity: 493
Merit: 518
I haven't been following this thread, so excuse the question if it has already been asked and answered:

Setting aside areas of technical disagreement for a second, what are the issues/areas for which there is technical agreement?

1. 21M coins
2. What else?
3. etc. ?

legendary
Activity: 3038
Merit: 1660
lose: unfind ... loose: untight
The problem is that these "other implementations" only have half-baked, horribly coded improvements.
Interesting assertion. I'd like to read your extensive code review of each such "other implementation".
There isn't an extensive code review of such an implementation by myself (probably not by anyone, as I haven't seen one).

Well, at least you admit when you are caught making shit up on order to influence a debate. Does that make you honest? No - it makes you a liar that has been caught in a lie.

Well, no. Segwit does absolutely nothing to make larger blocks safe.
Yes, it does actually, since there's no such thing as "The SegWit Omnibus Changeset".

Sure there is. You may not recognize it under that name. Hell, you may not recognize it at all. But there is certainly a difference between the feature 'Segregated Witness', and the bundled code release that includes several other features as well.

Oh - https://bitcointalksearch.org/topic/m.15417685
legendary
Activity: 2674
Merit: 2965
Terminated.
Bald assertion devoid of any supporting evidence is duly noted.
Fight fire-with-fire, or bald assertions-with bald-assertions when obviously reason isn't adequate.

Prove it? You can't even define it!
This is actually true. We don't even have a clear definition of 'spam', and yet some throw out the claims that blocks are filled with 'legit' transactions.

Your demonstrated pride in mastering this oh-so-advanced concept is simply adorable.
Sarcasm is pointless, and adorable is not an attribute worth pinning to this. A point has been made, and the point is correct.
legendary
Activity: 3038
Merit: 1660
lose: unfind ... loose: untight
It has been tested on testnet already. Stop spreading misinformation. There's nothing dangerous about bigger blocks.
The BU testing methodology is garbage and should not be used as 'evidence' for anything.

Bald assertion devoid of any supporting evidence is duly noted.

The blocks aren't full of spam
You can't prove this and you know it.

Prove it? You can't even define it!

Quote
I highly doubt you even understand the big O notation.

Your demonstrated pride in mastering this oh-so-advanced concept is simply adorable.
Pages:
Jump to: