Instance on GotoSocial updated to 0.21.0 #instanceadministration #instanceupdate #gotosocial
Instance on GotoSocial updated to 0.21.0 #instanceadministration #instanceupdate #gotosocial
And that's it, all done. With as minimal downtime as I could manage, as promised. #InstanceAdministration
As promised, here is your notification of impending downtime. #InstanceAdministration
Hi all. After a long wait, it's finally time for a Mastodon upgrade. All going to plan, this shouldn't take very long at all, maybe a couple minutes. I'll post when the downtime is expected to start. #instanceAdministration
Crossing my fingers and hoping that the changes I made to my GoToSocial config don't break things. It was mostly tweaking character limits for poll choices and media descriptions. Considering setting up S3 storage in the near future, but I figure I'll wait until my recent changes have settled a bit. #GoToSocial #InstanceAdministration #PollOptions #MediaDescriptionOptions
Question for other GoToSocial instance admins: If you're running a single-user instance like I am, does it make sense to have terms & conditions? I'd rather not make things more complicated than I have to. Already got some rules in place, so T&C's just feel like overkill. #AskFedi #GoToSocial #InstanceAdministration #TermsAndConditions
Will be some downtime in an hour or so while I upgrade the instance to mastodon 4.1.0. #instanceAdministration
Probably going to be some instance downtime within the next week while I work on implementing a proper backup solution and move much of our remote media handling to an ness3 bucket. Likely the biggest headake is going to be enginex, because I want to cache *some* remote media, just so we're not hitting the bucket every time. I'll post before this happens though, I just wanted to make everyone aware it was coming. #instanceAdministration