The RC-based system that blocks ops was published for review so that anyone with concerns about censorship could chime in and post about their concerns. It also gave people a chance to review the code to find any problems, which I'm sure wasn't the issue in this case since it was such a small change.
Imagine a situation where Steemit, Inc. worked on the RC system in secret, then release it with the expectation that everyone support it. The RC activation was rough enough, even with the opportunity to review. If it had been coded in secret, everyone would have pointed at that as being the reason for the rough rollout.
Anyway, like I said, testing is largely a moot point. I'll concede that a surprise update that does not freeze funds is a step in the right direction.
The problem I have with blocking ops is not the ops being blocked, as such. The RC system has a published and known criteria that applies to all accounts. It does not single out specific accounts. It only operates with criteria defined on-chain, albeit without consensus.
Therefore the general RC system is not in the same category and I don't see it as censorship.
All fair points. There is no perfect way through this situation. Something has to give, and in this particular situation the fact that Tron poses a real threat to the security of the blockchain combined with the fact that they already agreed not to use those operations made this an acceptable choice for me.