Topic: Article 2,Section 1, Articles of Federation of BU + Closed Source Patch!? (Read 1324 times)

Well, without providing the source upon reasonable demand. Did you make a reasonable demand for the source? Was it rebuffed?

Do you suppose all those digital toasters available at WalMart, with embedded graphics built upon Qt, ship with a full copy of the source code in the box? Or do the manufacturers just summarily fulfill requests for source in a reasonable fashion?

But in the moment, it's a good thing all the source is available on the repository, hunh?

You may not distribute a LGPL program as part of a single static binary without the corresponding source to the whole thing or object files for the parts so that you could link with a modified version of the LGPLed component.

You mean Qt? Isn't that mostly LGPL 3.0? In what way is the license violated?

They must be pretty embarrassed to have been consecutively attack just after launching there software and now they're are closing there source code cause they realize how buggy their code is.
They should really let the experts handle the job, bitcoin's algorithm has become extremely complicated they should really let it open source for the community to help them and find bugs that might cause trouble in the future.

Last time I checked hash rate providers would provide hash rate to a pool that charged a fee because it had less variance instead of earning more bitcoins at a smaller pool with less fee or no fee.

I spent 3 years on this forum trying to get hash rate providers to make better choices in order to promote a healthy Bitcoin network. What did they do? All go to one pool until it has > 50% of the network.

So, sorry if I don't really expect great things from hash rate providers.

last time I checked, miners can choose any pool they want.

FTFY!

QT.

Isn't it amazing , Greg?
 
Users and miners hate your Blockstream roadmap THAT much...BU hashpower still rising even after 2 node crash events.


 

'Almost all'? Can you be any more specific on the number?


Of which specific libraries was this a license violation?

There was exploit code for this latest crasher posted on the 13th, and people on the BU forums pointing to it... the "new" vulnerability was just above the old one in the control flow.

What was there to protect when almost all the reachable BU nodes were already down?

I can't think of a single piece of free software that has done this in the last decades, including highly critical software like OpenSSL. It's absurd. What BU did was also technically a license violation of some of the libraries.

I think the only thing left to debate is if they're trolling or if they're really that clueless.

::sigh:: once more, into the breech ....

agree its a PR nightmare but spare me the vitriol.  you know damn well it was closed source as a temporary patch while it was being reviewed and then released as open source the next morning.

BU IS DEAD FOR ME AND MANY SMART PEOPLE! Have no idea who made this panic with this shitty BU!

Closed source patches are a disaster. Nothing but PR nightmare from a technical point of view. BU released buggy code and  was criticized.
So their answer is to this problem is making development process hidden from the pubic eyes? LOL
Instead of earning trust of the users they want to usurp it by forcing everyone to accept their code unconditionally.

There is more: the closed source binaries weren't signed, which means, any hacker could hack the bitcoin unlimited website and perform a man-in-the-middle attack infecting your computer and stealing your BTC. Pretty simple actually, with the morons in charge of BU.

Do not shoot people's opinions down and point fingers to shilling every time they have a opinion on a subject. If you check my post history you

will see I am not a big BU supporter, but rather warming up to the idea that Bitcoin Core might work.... but I still debate the issue and discuss

the matter from many angles. We sometimes have to step back a little to see the bigger picture... you get caught up in your own opinions and

you leave no room for other ideas and proposals. We should have ONE goal and that is to find a way to scale Bitcoin in the safest manner

possible and I think the Core developers are up to the task. I will still entertain other people's views and opinions. 

Another FUD post from Franky1, i wonder how much you get paid for each post you make. It contains a lot of nonsence.

but if truly independent then there are no factions.
but by people saying bitcoin is
dependant on core devs - bitcoin weakness
core devs are not independent - bitcoin weakness
bitcoin should only function with one codebase - bitcoin weakness

my personal opinion is that there should be a dozen different implementations wrote in atleast half a dozen different languages. that way if one has an exploit.. only a few % go offline(like this month)... not 1-2 codebase where big orphan chains and lost transactions and double spends occur(like 2013)

where by consensus (real node and pool consensus) settles on features to improve the network. non of this go soft then blame pools. then blaack mail pools with bilateral splits bull crap


p.s
im not in cahoots with any brand. i kiss no asses. and i think thats what people do not like about me. i am frank about what i say, and i dont kiss asses.. devs can come and go. but thats why a diverse open decentralised network should remain higher priority than sucking up to Gmaxwell.

but i laugh when people confuse my desire for diversity and other options that are not just core.. by trying to pigeon hole in whatever latest REKT campaign cor try to do to keep them ontop.. because it just digs them people into bigger holes by admitting they want centralism