While I’m skeptical there are many people still using fedia.io, I have been continue to try to fix the error 500 problems. These errors are caused by kbin thinking it stored database records with pointers to images (like the avatar image, images attached to posts and the like) but not actually finishing. So when certain records are pulled up (magazines or posts or users) where there is a missing image record, an error 500 exists. I’ve continued to find more instances of this and frankly I don’t know what is causing the problem. As a mitigation, I have been running cron jobs every 15 minutes to correct these broken links. This morning, I believe I chased down the cause of the last remaining disconnect and have that being fixed as well.

I suspect there are still other problems, like replies appearing twice. I will try to figure out what is going on with those as I can.

    • all-knight-party@fedia.io
      2·
      10 months ago

      That explains why it was never fixed, the admin running the server seems to have disappeared a week or two before i joined the instance and I haven’t seen hide nor hair of them, I even sent them a PM about that issue, but never heard anything back. Considering Fedia still has some issues and even testing the waters recently I’ve been logged out by the “invalid csrf token” problem, I think I’ll just try a different instance again, kbin.run is seeming all right, relatively small, but the owner has been recently active and is updating the instance, even directly posting about the avatar upload bug.

      It’s surprising, actually, just how few truly active kbin instances there are, and I love the hell out of Jerry, but I think he’s got too much on his plate to properly fix up Fedia at the moment, at least, not until kbin is less buggy and he has the time to spare from his many other projects, I hate to step away from Fedia, but since I quit reddit cold turkey and don’t use any other social media whatsoever I’m really relying on a baseline level of usability for all features.