I was live testing a fix for a different 500 issue and I might have accidentally caused 500s to be generated elsewhere… should be stable now. If the site is acting stupid, there’s a 99% chance it’s because I’m either live testing a code change or messing with something else in the background.
Sorry for any interruptions and happy holidays!
Definitely agree we shouldn’t be 500ing, sounds like an error needs to be fixed, so we should investigate. If there are any examples of the instances / accounts on when it happens, that might help. One thing I’m wonder is if this is related to authorized fetch as I think I remember that causing errors for kbin/mbin when trying to follow mastodon accounts, but if they work eventually then perhaps it isn’t that