Main developer cant force users to anything, aside from auto-updating all Android apps through Google Play store (but not those in coming F-Droid release, how is it coming along @portabella !?)
To be honest, I do not know what would happen if I ran a modified client today which said it has 15 witnesses, I guess it would just be dropped as invalid transaction.
If i wanted to I could start a new network, "a fork" with 15 witnesses, but its then only using the same software but not at all same.
The concept of forks is discussed in the whitepaper under the title Schisms - in Byteball it is necessary for a new network, a new Byteball in the cases when witnesses collude with each other or just loose trust by the majority users - they can then start their new network, with 13 witnesses or 12, and begin linking old bytes to the new network as is being done today from BTC to Bytes.
What I like about Byteball is that the users have so much power. Just by selecting what to use, which witness we trust. Simple.
EDIT: Just to be clear, there is weakness in Byteball in my opinion, though CfB is clearly off target by half a planet. So far its only a few developers who understand it, we need better documentation so more developers can join and begin developing apps.
Thank you again. It would be nice if someone can comment on what happens if byteball.com owner decided 15 witnesses is too much and 15 witnesses will lead to bigger fees, less transactions and adoption, so they made a client with 9 witnesses.
How network would resolve how much witnesses is fine, or it will just split in three independent byteballs.
I'm not affiliated with CfB, btw, and not shill for iota, just curious
