Sort:  

When the fork happened, the platform completely shut down. I was reading that many nodes were not on the latest version, so I went in and unvoted anyone that was not running the most current code. I did not do this at first. It was after more than a day of chaos. I have not been back to the list since that day.

The platform, hive.blog, is still not working. One in twenty attempts to post or comment succeed, votes are not marked as such and then error when I vote saying I already voted, and it has been more than a month.

If the platform every gets back on track, I will go through the list again and evaluate witnesses using the criteria that I have always used.

If it does not, I will be selling out again (just finished dumping all my steem) and moving to something that works.
-Patiently waiting-

Updage: This comment did go through via hive.blog, I was all set to post via peakd if not.

That is understandable, this was a big fork on the technical side with a lot of changes which made node requirements much smaller and cheaper to also run RPC nodes which we intend to get going. When you say "running most current code" I just gotta let you know that some who are running newer code like 1.24.4 or 1.24.6 that it's not mandatory if that was what you meant, cause we've been on 1.24 for a few weeks before the HF took place and ready for it.

About the selling, yeah, I'd recommend not doing it because of these current API issues as long term the platform will be improving a lot more and will be streets ahead of its predecessor, although I do expect them to copy much of the code once it's more stable. Hopefully hive.blog can let people choose between more nodes in the near future like peakd does as well.

Anyway, nice to see you're still active yourself, thought maybe you had someone else doing the curation passively and hopefully you'll stick around for a brighter future - at least price and traffic wise.