@IceRock@glaceon.social
Hey everyone! I'm going to be updating the instance at 5:00 eastern, about two and a half hours from when this post is being sent.
This update is going to be a little bit more involved than most of them are due to a couple breaking changes in stuff on the backend, but I don't anticipate major problems. Still, it is going to mean at least a little bit of downtime, and I can't make promises about exactly how long. Let's be really conservative and say an hour, though it'll probably be less than that.
If I have anything I need to say while the instance is down, I'll be saying it on Amy's account at .
okay. holy shit. i am so sorry
If you've been following what I've been posting on Amy's account you'll know that the update process was an absolute nightmare. Don't get it twisted, it's my fault, this is not because of anything unreasonable done by the Mastodon developers. In fact, I got quite a lot of help from a Mastodon developer who I will refrain from naming here in case they want to be left alone, but I really do appreciate them being available to answer my "hey should this be like this, how do i fix it" questions last night and this morning. Otherwise I'd probably have had to resort to the nuclear option of "spinning up a whole new server and restoring a database backup there", which I very much did not want to do.
I suspected there would be some difficulties due to choices I'd made in the past, but naively thought that working around them for now was going to be much easier than it was. My plan was to fix things properly over the weekend, since I knew that would take some time, but... my paw was forced. I ended up having to do the correct and hard thing just to get the server back at all.
Anyway. We're back, I'm sorry again for the inconvenience. This has got to be my worst ever estimate for the duration of scheduled downtime here, and hopefully it doesn't get that bad again.
It may be a bit slow to see new posts come in, or to receive notifications. That's only because the server still has quite a lot to catch up on, and it should resolve itself with time.
As an additional heads up, there will be downtime for another update tomorrow, at 10 AM eastern! Fortunately, the whole reason I did this update was to make sure that one goes as smoothly as possible. So I don't predict nearly the same level of difficulty as the update I just did. Yes, I have knocked on wood.
