submitted 1 week ago* (last edited 6 days ago) by [M] to c/meta@slrpnk.net
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 week ago (1 child)

Hello! I just found this thread. I also have a fork of mlmym, based on the FHF version, at https://code.mschae23.de/mschae23/mlmym. I'm also working towards support for the v4 API of lemmy 1.0, but progress is slow :)

I hope you don't mind this bit of self promotion.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 6 points 1 week ago (1 child)

    Thanks for sharing and keeping it alive.

    May I ask how much of it is LLM generated?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 1 week ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 7 points 1 week ago* (last edited 6 days ago) (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 6 days ago (1 child)

    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!

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 5 points 6 days ago (1 child)

    Ah, excellent, these are all good. Thanks for the heads up.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 6 days ago (1 child)

    Hm, I was looking at your instance right now and saw that the top bar is missing the community list. Someone already reported this a while back, but I was never able to reproduce it. Unfortunately, error logging is rather barebones, but maybe there is something relevant in the logs that could help figure this out?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 4 points 6 days ago (1 child)

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

  • source
  • parent
  • hideshow 2 child comments