Statements can be conditional or situational. Take, for example, "The sky is blue - agree/disagree". Sounds simple enough, right? But what about sunrise/sunset? What about the night? It's not always blue and, as such, is a flawed statement. So I would phrase it "The sky can be blue" - agree/disagree"
but then your not stating what it cant be(silver)
That's not the question I'm asking.
And again, I've given you free reign to remove any ambiguity if you feel you can give a more precise statement. I'll highlight some of the reasons why I haven't used absolutes in some areas and request clarification from you about each specific question in regards to the issue you have:
Consensus:8. Any developer is free to code what they want. [color="444444"]<- This is an absolute statement. Please highlight in what way it is "open" or "uncertain".[/color]
agree[ ] disagree[ ]
9. Everyone will be free to run any code they choose. [color="444444"]<- This is an absolute statement. Please highlight in what way it is "open" or "uncertain".[/color]
agree[ ] disagree[ ]
10. If enough people run code with different consensus rules, change can happen even if a minority disagree. [color="444444"]<- If I had said "change
WILL happen", this statement could be flawed. As an example, the required activation threshold may not be met for one particular proposed ruleset if multiple different proposed rulesets are being run concurrently.[/color]
agree[ ] disagree[ ]
11. If you run code which is incompatible with the code a majority of users are running, you can be disconnected from the network. [color="444444"]<- You are free to state "you
WILL be disconnected" if you like. However, you would need to be confident there are no exceptions to that statement. I'm happy to leave margin for error, but you aren't compelled to.[/color]
agree[ ] disagree[ ]
12. Features implemented by soft fork can be considered "opt-in" and you can continue to remain part of the network even if you don't want to use those features. [color="444444"]<- To say "you
WILL continue to remain part of the network is incorrect, as someone may choose not to remain part of the network. Anyone is free to leave the network at any time.[/color]
agree[ ] disagree[ ]
13. If you are unhappy with the current consensus rules, there is no onus on any Bitcoin user to surrender to your demands. [color="444444"]<- Please highlight your issue with this statement[/color]
agree[ ] disagree[ ]
14. If anyone wants features which are wholly incompatible with current consensus rules, it is reasonable to suggest they consider looking at other projects geared towards that purpose. [color="444444"]<- Please highlight your issue with this statement[/color]
agree[ ] disagree[ ]