Quote from: Holliday on March 24, 2017, 11:22:53 PM

Quote from: franky1 on March 24, 2017, 11:18:48 PM

blockstream

Life must be so simple when you don't need valid arguments, just a bogeyman.

like blockstream fanboys cannot defend the half promises of segwit that wont be met and the empty temporary bribe gestures, etc.. they instead find their own boogeyman, such as blame the pools for blockstreams removal of reactive pricing(replaced by average) removal of priority(replaced with just pay more) and refusing to expand REAL blocksize(replacing with empty promises of more tx if segwit happens)
yet all the finger pointing can find its way back to blockstream caused events

well when nodes HAD the power to veto. pools had to follow nodes lead or get orphaned.
EG

Code:

2017-01-29 06:59:12 Requesting block 000000000000000000cf208f521de0424677f7a87f2f278a1042f38d159565f5
2017-01-29 06:59:15 ERROR: AcceptBlock: bad-blk-length, size limits failed (code 16)

boom non consensus block dealt with in 3 seconds. drama over
...
but now blockstream used a loophole to give pools the power(going soft).. and if pools dont kiss blockstream ass blockstream can kill the pools.

also segwit(blockstream) wants to widen their loophole(going soft even easier in future) to make it even easier to throw trojans in without node consent/veto.
and again blame pools if anything bad happens or kill pools if they dont do as blockstream say.

if blockstream had any honour. they would see there is resistance and instead of threats of lowering bip9, doing UASF and mining algo changes.. they should honourably re thing and compromise themselves to something the community would accept..
but no its blockstreams road or the cliff