While 22.2 could be considered an escalation...
It broke the trust of the Chain by individuals restricting account options on specific accounts, as opposed to a universal change, like no powering down for anyone.
It was an escalation by witnesses taking arbitrary decisions against specific accounts. There is EOS for that kind of shit.
It was a decision to guard the integrity of the chain and the project, in the face of numerous instances where the perpetrators of the 22.5 hack had disclosed plans to dissolve steem.
It just pissed off a billionaire from my perspective.
That it's now possible to successfully go against people with a lot of money and have them beg for mercy instead of having the unlimited power they used to have.
Basically this is exactly why we have P2P tech right? This will prove why we do this in the first place...
Also I'm very curious about how hive.io will be doing soon!
LOL. Yes this should be
Very interesting to
See how things play out.
- novacadian
I'm a bot. I detect haiku.
We are in the position not just to have a fighting chance, but to be a significant force where historically this would have been "solved" with money before anyone would even know. The man with the money is not in need of empathy. This is justice in its purest, and we should deal with it apropriately. Not bending over as a community.
O I see, so they should have went along with his plans to dissolve steem, because billionaires?
Heck, no. My point; which seems to have been missed; is that v. 22.2 achieved nothing, nothing and more nothing EXCEPT to piss off a billionaire.
Nope. If the trust of the chain was to be broken, as to me v. 22.2 is considered to be, then go all in. Not a rebranding but get a couple of exchanges to run a 22.4fuckyouCAPITALIST fork which had @null|Mr. Sun in the code. Pay the exchanges in BTC to recreate the chain. They sure as shit would have for BTC. Then STEEM would have been saved.
V. 22.2 did not save STEEM.
HIVE is not saving STEEM.
Now there will be most of Hive that will say that the community is saved. Well that may be. But much was lost that may never be regained. Google's indexing just for one. A conscious community effort must be undertaken to fix this one. It could be helped a great deal by redirecting one's blog postings on STEEM to the copy on HIVE. Not 100% sure on that. Have not checked if redirects work on STEEM as well.