Re: [Taproot softfork] lukejr removing option to lock-in on timeout... :D
I think that it was clear in my post as 14 people were fine with either choice 
I agree with this actually. I don't see the need for signaling if you can just choose to run the code or not. I'm not a coder, but I understand the concept of simplistic code being better. Running the code should be the signal. This whole signaling after you install the update makes no sense to me and seems over engineered. If you don't run the new code, then you are signaling you don't support the changes.
Very well said, I could not have found a better way to express that, which is what I think too. Only problem I see is the very long wait: August 2022 is too far way, too many things can happen in this huge timeframe.
someone (Matt Corallo, a Bitcoin dev) suggested that. But his proposal was just to activate the fork the simplest way: Bitcoin 0.21.1 would just start enforcing the fork after August 1st 2022. No signals, no percentages. Either you're running the new code or you're not.
I agree with this actually. I don't see the need for signaling if you can just choose to run the code or not. I'm not a coder, but I understand the concept of simplistic code being better. Running the code should be the signal. This whole signaling after you install the update makes no sense to me and seems over engineered. If you don't run the new code, then you are signaling you don't support the changes.
If date August 2022 is arbitrary, what is stopping core from making it January 1st 2022 or some other date?