Well, if they will succeed, then it will be also used in that way. Because if you can block spammy transactions, and it will work, then you can block any transaction, by using the same methods. And then, the only thing you would need, is to convince people, that "mixing coins is a spam", or "sending coins without AML is a spam", or that anything you want to censor is a spam. Just call it a spam, use the same methods, and voila, you have a great censorship tool, working way beyond "spam", which can be used to block regular payments between users, in exactly the same way. I don't know, maybe Luke should just run a signet instead, and everyone should ask him for permission, to use a coin. Because you never know, maybe when he will see your Script, he will call it a spam, and block it? There should be a table somewhere, like "use cases approved by Knots", to let users know, which use cases won't be blocked. Because otherwise, it is highly subjective, what will be blocked in the future, and what will be allowed. And how people can be sure, that it won't be blocked, when OP_IF can be rejected? Where is a list of all allowed use cases? There should be something like that on Knots pages, because otherwise, you can use something today, and tomorrow, Knots users can block it, and call you a spammer. If there would be such a list somewhere, then users could at least say: "you allowed me to use it in that way, so don't try to block it now".
Well, if they will succeed, then it will be also used in that way. Because if you can block spammy transactions, and it will work, then you can block any transaction, by using the same methods. And then, the only thing you would need, is to convince people, that "mixing coins is a spam", or "sending coins without AML is a spam", or that anything you want to censor is a spam. Just call it a spam, use the same methods, and voila, you have a great censorship tool, working way beyond "spam", which can be used to block regular payments between users, in exactly the same way. I don't know, maybe Luke should just run a signet instead, and everyone should ask him for permission, to use a coin. Because you never know, maybe when he will see your Script, he will call it a spam, and block it? There should be a table somewhere, like "use cases approved by Knots", to let users know, which use cases won't be blocked. Because otherwise, it is highly subjective, what will be blocked in the future, and what will be allowed. And how people can be sure, that it won't be blocked, when OP_IF can be rejected? Where is a list of all allowed use cases? There should be something like that on Knots pages, because otherwise, you can use something today, and tomorrow, Knots users can block it, and call you a spammer. If there would be such a list somewhere, then users could at least say: "you allowed me to use it in that way, so don't try to block it now".

Well, if they will succeed, then it will be also used in that way. Because if you can block spammy transactions, and it will work, then you can block any transaction, by using the same methods. And then, the only thing you would need, is to convince people, that "mixing coins is a spam", or "sending coins without AML is a spam", or that anything you want to censor is a spam. Just call it a spam, use the same methods, and voila, you have a great censorship tool, working way beyond "spam", which can be used to block regular payments between users, in exactly the same way. I don't know, maybe Luke should just run a signet instead, and everyone should ask him for permission, to use a coin. Because you never know, maybe when he will see your Script, he will call it a spam, and block it? There should be a table somewhere, like "use cases approved by Knots", to let users know, which use cases won't be blocked. Because otherwise, it is highly subjective, what will be blocked in the future, and what will be allowed. And how people can be sure, that it won't be blocked, when OP_IF can be rejected? Where is a list of all allowed use cases? There should be something like that on Knots pages, because otherwise, you can use something today, and tomorrow, Knots users can block it, and call you a spammer. If there would be such a list somewhere, then users could at least say: "you allowed me to use it in that way, so don't try to block it now".

Well, if they will succeed, then it will be also used in that way. Because if you can block spammy transactions, and it will work, then you can block any transaction, by using the same methods. And then, the only thing you would need, is to convince people, that "mixing coins is a spam", or "sending coins without AML is a spam", or that anything you want to censor is a spam. Just call it a spam, use the same methods, and voila, you have a great censorship tool, working way beyond "spam", which can be used to block regular payments between users, in exactly the same way. I don't know, maybe Luke should just run a signet instead, and everyone should ask him for permission, to use a coin. Because you never know, maybe when he will see your Script, he will call it a spam, and block it? There should be a table somewhere, like "use cases approved by Knots", to let users know, which use cases won't be blocked. Because otherwise, it is highly subjective, what will be blocked in the future, and what will be allowed. And how people can be sure, that it won't be blocked, when OP_IF can be rejected? Where is a list of all allowed use cases? There should be something like that on Knots pages, because otherwise, you can use something today, and tomorrow, Knots users can block it, and call you a spammer. If there would be such a list somewhere, then users could at least say: "you allowed me to use it in that way, so don't try to block it now".