You mean forking the code to create a new option, in addition to Core and Knots? Not a bad idea. I think there is a need for that, from ones careful enough not to create accidental hard forks.

Why does Core have to make it hard for node runners to revert the change, by removing settings that would give them that ability? Should a whole new version be needed, when the settings could have been retained?

This is seriously your answer to that? Really?

I love how you moved the goal post from "they aren't removing choices" to "well, luke is adding features you might not like either" 👌 *just* revert one change Thats LITERALLY the change we are talking about. But go on call people "Knotsi" and make them seem crazy for wanting to have better control over the software they run.