Quote from: franky1 on April 08, 2019, 10:35:10 PM

Quote from: hv_ on April 08, 2019, 09:19:25 PM

Designing a protocol does not need devs. Btw. Maybe refactoring and bug fixing, but the consensus is dev free territory

bitcoin is digital.
it is code
CODE
not conversation

code does not write itself
devs write code
for a new rule to be proposed devs need to CODE it
if devs CODE it in a way that controversially 'sends off' a controversial amount of users then you cant pretend the devs were not involved

i really find it funny that people think bitcoin is just social drama and such are only interested in performing social drama rather than speak about actual code and actual protocols.

smtp, tcp/ip whatever are specked designs at first place. Coming from ideas - nothing to do with code at initial state

Sure, if u start impl that ideas very local and concrete - into a Client (Server) that want to communicate with others u need to make ur APPLICATION impl
into that consens

I agree with bitcoin to get the basics done - there is many impl needed - but if u start changing the consens protocol by changing code first, and break the initial design by that , ur doing wrong since u brake the consensus with base protocol code dev. Better to move these things into APPLICATION layers and keep the consensus as thin & simple as possible.

Devs write APPLICATIONS that follow initial protocol DESIGN / SPEC

Edit: And BTW if ppl try to limit scaling by protocol design for a global protocol ( and dev it into ) they ve some screws lose.