As you likely know we are running several alternative web front ends for Lemmy. Currently they are:

Of these Alexandrite and Mlmym have not been updated and maintained for more than one year now and the original authors have likely lost interest. I also assume that once we upgrade to Lemmy 1.0 they will stop working properly.

In addition I think only Photon and maybe Voyager have added support for the Piefed API, should we switch to that in the future (but it seems like Lemmy 1.0 might solve our main technical concerns with it, and the memory consumption recently got quite a bit better).

So all in all, we will probably sunset Mlmym and Alexandrite soon.

There is also a new frontend called Blorp that we could set up. It seems quite nice, but also very similar to Photon. But let me know if you are interested in using this frontend.

Edit: I was made aware of an somewhat maintained fork of Mlmym that we are now using, so that one can stay a bit longer then.

Edit2: We switched to an even better maintained mlmym fork that even plans to support the Lemmy 1.0 api v4, so I think that one should be good to keep for a while.

      • mschae@discuss.mschae23.deEnglish
        8·
        9 days ago

        Everything I’ve done was written entirely by me, as I don’t use AI on principle. I’m fairly sure it was used by some people to contribute to the FHF fork (I’ve seen CLAUDE.md added to gitignore), and the readme and docs did have that AI-generated “feel” to it, if that makes sense. That’s mostly why I reverted them to what it looked like in rystaf’s version in that commit. I couldn’t tell whether AI had also been used for code, so I left that unchanged.

        • poVoq@slrpnk.netOPMEnglish
          7·
          9 days ago

          Ok great, that is what I hoped to hear 👍

          I’ll try your fork later today and see if there are any issues. Thanks again.

          Edit: Nice, seems to work quite well. I’ll also try switching to Iocaine in front (edit: done), so that we don’t have that Javascript barrier in front of it.

          • mschae@discuss.mschae23.deEnglish
            3·
            9 days ago

            Nice! I don’t know if you’ve done so yet, but I recommend enabling some options by default: SHOW_UNREAD_COMMENTS (this one is really useful!), LANGUAGE_TAGS, SHOW_CONTROVERSIAL, and, if you want it, EMBED_METADATA. They’re just environment variables, set to 1 to enable.

            If you have any questions or problems, feel free to reach out to me!

                • poVoq@slrpnk.netOPMEnglish
                  4·
                  9 days ago

                  Nothing that seems relevant in the server logs here either. Maybe a side effect of setting LISTING='Local'?

                  • mschae@discuss.mschae23.deEnglish
                    4·
                    9 days ago

                    … I didn’t expect the problem to be that simple 😅

                    I’ll have a fix soon.

                    edit: I’ve published 26.3.3, which should fix this issue.