feddit.de has been giving “Server error” for some time but I read that the server is still working when using a Lemmy app. Tried the Photon front-end today and choosing feddit.de as instance.

My question (I’m just curious, I have no account on feddit.de) is : Can an alternative front-end on their server co-exist with the other server software ? I guess it would be a matter of installing Photon and then point nginx configuration to that. Or am I missing something crucial ?

  • Titou@sh.itjust.works
    0·
    5 months ago

    I created my first lemmy account on feddit.de, it was in july 2023, and since some months i was unable to access to my account on pc but worked on Voyager. Tired, i decided to switch to sh.itjust.works

    • lemmyreader@lemmy.mlOPEnglish
      0·
      5 months ago

      Unfortunately the feddit.de server has been broken for quite a while and we have trouble contacting the admin.

      Oh, that explains it.

    • B0rax@feddit.de
      0·
      5 months ago

      There is a matrix channel where the admin is answering from time to time. But he is currently very occupied with real life stuff. And he is also the backup admin, as the original admin is currently on a workation on the other side of the globe and seems to be unreachable…

  • Charlotte_Thomassen@monyet.cc
    0·
    5 months ago

    Lemmy front-end can be anywhere, it is front-end. It is an app install on your computer. Think, front-end is an app like mobile app on your phone. But front-end is on internet because it is a web-app, you got to download it first. THen your browser cache it.

    Some instance host front-end for convenient, but you can access front-end from the project homepage.

    For example: to use alexandrite front-end access lemmy.world, you can

  • taladar@sh.itjust.works
    0·
    5 months ago

    It is not that the regular frontend doesn’t work and alternative frontends do, it is that half of the stuff on their server (including image uploads and the frontend) don’t work because the admin has no time to deal with it. The problem isn’t the software used but the lack of maintenance.

    • Victor@lemmy.world
      0·
      5 months ago

      Isn’t there a software issue if it breaks with time unless you maintain it? What has happened more specifically? Memory leaks?

        • Victor@lemmy.world
          0·
          5 months ago

          Good point, didn’t think of that. That’s not an issue with the software. Although, one could argue that it should not break down and become unresponsive.

          • taladar@sh.itjust.works
            0·
            5 months ago

            A lot of software writes to log files or temporary files or lock files or database transaction logs as part of its normal function and when those writes fail due to a full disk the software doesn’t work anymore.

            • Victor@lemmy.world
              0·
              5 months ago

              That’s bad software then, right? The inability to write to disk shouldn’t cause the software to lose all functionality. Unless that’s its only function, or somehow depends on it for proper functioning. 🤷‍♂️

              • Jarvis2323@programming.dev
                0·
                5 months ago

                No. Every good software program should write at least logs to disk. Every good database writes to disk. Add a new post, db will commit to the db and the db will grow in size.

                Name any decent sized program where new content is added and I guarantee it writes to disk and will fail eventually if not maintained.

                • Victor@lemmy.world
                  0·
                  5 months ago

                  Nice down vote. Let’s discuss instead.

                  I’m saying that the server shouldn’t go down just because new content can’t be added. You should get maybe a 500-series REST response or something. Not… nothing. Ideally it should write to disk. Ideally it should allow new content to be added. But uptime and content access is still more important than being able to write to disk. It should warn the admin of the serious errors, and explain to the user in some diplomatic/apologetic manner. But never go down completely. That’s not resilient at all.

                  That’s my opinion. 👍

      • KISSmyOSFeddit@lemmy.world
        0·
        5 months ago

        The server’s hard drive filled up completely from image uploads, which in turn corrupted the database.
        By the time the admin noticed it and had time to troubleshoot, the automated backup process had replicated the corrupted database, overwriting all backups that had a still-functioning database.
        There was some personal event in the admin’s life as well as a long planned vacation at that time.

        The lesson to be learned here is that a private server administrated by a single person in their spare time isn’t something you can rely on.
        The Feddit community is currently trying to found an organisation that can share the administrative load and is able to receive donations.

        • Victor@lemmy.world
          0·
          5 months ago

          hard drive filled up completely from image uploads, which in turn corrupted the database

          This is so baffling to me. How does this happen? There needs to be checks in place so that this can’t happen ffs lol. No space left on the device to complete the write? Abort. Or like, starting to run out of space => stop accepting new content until fixed, to protect the integrity of the data. Something.

          Anyway, I hope they manage to find a solution to sharing the load of work! 🙏😌

          • KISSmyOSFeddit@lemmy.world
            0·
            5 months ago

            You can set up safeguards against this. You can also make sure some of your backups are never overwritten. But you have to do it in advance.