here we go again you poke, i bite.
shame you are missing the point of decentralisation
they had segwit roadmap plan from 2014. before community input
they had code before community got to download.
Which means someone made a compelling argument about the idea and most of the developers in that team agreed with it. Ideas can come from anywhere, including from developers themselves. Saying that developers shouldn't work on an idea just because a developer proposed it isn't a mature or realistic stance.
^ their internal circle agreed. before letting the community have a say
i guess you missed the 2014-5 drama.
v not letting the community be involved is prime example of centralisation
I don't know where you get this perverse notion that developers need permission from the community before they are allowed to code something.
do you ever wonder why i just publicly give out idea's and let people decide yay or nah. rather than keep idea's in secret and make code and then demand adoption. again before trying to say im demanding anything. show me a line of code i made that had a mandatory deadline that would take people off the network if not adopted.
.. you wont. there is no need for your finger pointing that im an authoritarian demanding rule changes. because there is no demanding rule changes made by me
i find it funny that you flip flop about community involvement.
my issue is that they plan a roadmap. code a roadmap. release it and even if rejected, they mandate it into force anyway
emphasis.. MANDATE without community ability to veto
again the point your missing
having code that allows community vote/veto (2016, good)
having code that mandates activation without vote/veto (2017, bad)
you do realise that core could have had segwit activate by christmas 2016 if they just actually went with the 2015 consensus(early variant of segwit2x). which was a consensus compromise of the wider community finding agreement
which gave legacy benefits too.
but by avoiding it. and causing drama all the way through 2016 of how they want it only thier way(segwitx1).. pretending they couldnt code it any other way
they still didnt get a fair true consensus vote in their favour in spring 2017. so had to resort to the madatory activation and swayed the community is (fake) option of segwit2x(nya) just to then backtrack to segwit1x once they got the segwit part activated