Never ever fork peoples stake away. And never suggest it in any way shape or form. This kind of behaviour is a violation of property rights and will scare away potential future stake holders.
Never ever fork peoples stake away. And never suggest it in any way shape or form. This kind of behaviour is a violation of property rights and will scare away potential future stake holders.
I would ask you to look at the fact that I haven't forked (even though I didn't "get what I wanted" as some would say) as an indication that I am not going to toy around with these things. I do though still reserve the right as a witness to adopt any hardfork that I truly believe is in the best interest of the stakeholders and platform, and in absolutely extreme situations - that might include freezing somebody's account.
Here is one example to think about - if an exchange has more than enough STEEM on it to be able to single-handy take over all of the top 20 witness votes and they get hacked by a malicious actor who wants to destroy Steem - I would seriously consider it in that case. You can start to get less black and white - let's say that Steemit, Inc. somehow got "taken over" (not hacked) by a group of people that wanted to adopt a hardfork that would somehow screw over all the other stakeholders. Again, I might seriously consider it in that case too. Where does the line get drawn?
Honestly, it is a really difficult question. And a serious one too. Part of me would love to just take a simple "I will never do it" stance, but honestly - I feel that it would be irresponsible to do so. I take my job very seriously, and I reserve the right to use whatever tools exist in my tool-belt if I deem them necessary to do what is best for the Steem stakeholders.
The point is, it is not always black and white, and I am not going to make an on-chain commitment to never consider using it as a tool. I am also not going to cloud up a post which had a specific intention (to ensure Steemit that their funds were safe if they didn't power down) with a long drawn out explanation of when I found it appropriate to use this type of hardfork as a tool.