PeakD has made an update so that the node used to display information will auto switch now so people don't need to keep chasing the node/api issue.
The switching has lessened, but after I click reply.. I will get an error.., I can't remember any other HF having problems for this long after it happened. Things are generally cleared up after 2-3 days.
Those errors are from outgoing action, so the method used to sign in, Hivesigner, Hive keychain, or peaklock. There ae still a few issues with hivemind acting up, blocktrades expects the majority of the hivemind issues to be fixed by Monday.
When you get the error if you are on peakd go to the bell, (notifications), and click the resubmit icon the counterclockwise circle arrow, most of the time when I do that it works, beasts copying the reply and then pasting it and hoping it go through the next time.
It seems that the witnesses and the dApp people did not do enough testing with the calls to the API's and Hivemind. It's a pain right now, but should really help out the application builders in the future.
I haven't been bleating too much about all the little problems because I figure people who know about back ends are working on it, but yeah it's a bit ballsed up still...
I listened to the Developer video meeting minutes that @howo put up, blocktrades seems to think that by Monday most of the issues with Hivemind will be resolved, but then the applications will need to play catch up and do some fixing also.
The tools page for PeakD was down for a day and a half or so, but @asgarth was able to get it repaired. I am not sure how other apps are doing it, if they are waiting or working on things at the same time.
If this was still the Steem chain, steemit would just do fork after fork, I was not there for the first years worth of forks I came in about a year after start-up, and into I think HF17 or 19, not sure which one, but they had a lot of forks that first 12 months on Steem.