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!

  • 13@kbin.run
    2·
    6 months ago

    @[email protected] I’m not sure but I think I get a 500 error whenever I follow a user on a mastodon server that hasn’t federated with kbin.run yet, that is if I follow five people from the same new instance I only get the error for the first one.

    • debounced@kbin.runOPM
      2·
      6 months ago

      hmm, that sounds like a kbin “bug” that’s been around for a long time… we ought to change how this is handled in Mbin since I don’t think we should throw a 500 for this condition, a better message like: “i’ve never seen this instance before, give me a second to pull it in” instead of giving up right away… or make it asynchronous so the user doesn’t have to hit the follow button again.

      @e-five, what do you think?

      • e-five@kbin.run
        2·
        6 months ago

        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