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.

all 31 comments

sorted by: hot top controversial new old
[–] 7 points 3 months ago* (last edited 3 months ago) (11 children)

Is there a significant server load difference between the different front ends (including local ones like Boost/Jerboa on Android)?

PS: Also, looks like Fedihosting-Foundation-Forks is maintaining a fork "on limited life support" of mlmym to support the instance at old.lemmy.world, its last commit was 5 months ago.

  • source
  • hideshow 11 child comments
  • [–] [S] 8 points 3 months ago* (10 children)

    They all call the same API, so it should be mostly the same.

    I didn't know that there is a fork, thanks for sharing. I'll probably update to that one first then (Edit: done). I rather like to keep a version for old PCs or browsers available.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 6 points 3 months ago (9 children)

    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 9 child comments
  • [–] [S] 6 points 3 months ago (8 children)

    Thanks for sharing and keeping it alive.

    May I ask how much of it is LLM generated?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 8 points 3 months ago (7 children)

    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 7 child comments
  • [–] [S] 7 points 3 months ago* (last edited 3 months ago) (6 children)

    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 6 child comments
  • [–] 3 points 3 months ago (5 children)

    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 5 child comments
  • [–] [S] 5 points 3 months ago (4 children)

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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 3 months ago (3 children)

    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 3 child comments
  • [–] [S] 4 points 3 months ago (2 children)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 months ago* (3 children)

    My experience is, I try the frontends out every month or so but always go back to plain (browser, on mobile and desktop) because some feature is missing or off

    I like how they look though! And am frontend curious — just haven't seen one I like more then default web experience yet

  • source
  • hideshow 3 child comments
  • [–] 5 points 3 months ago (2 children)

    Lemmy ui in 1.0.0 is really good tho

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 months ago (2 children)

    I'm not sure if it's related to your two updates or not but, within the last week or so, my load time loading into this instance on mobile and on voyager have been cut in half. It was taking forever there for a bit. Now it's the same as any other instance I load. So yeah, idk the tech answer but, things have improved!

  • source
  • hideshow 2 child comments
  • [–] [S] 4 points 3 months ago (1 child)

    Yeah the server the reverse-proxy runs on was overwhelmed dealing with AI scraper requests in a strange feedback loop with Anubis. I am almost a bit suspicious if this is intentional to discurage the use of Anubis, but for now these scrapers seem to be fine with ingesting the garbage that Iocaine serves them, so at least temporarily our instance behaves again like expected.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 3 months ago

    I'm just using boost on mobile and am barely on desktop, so not many opinions from me.

  • source
  • [–] 2 points 3 months ago (9 children)

    Photon has never worked for me in mobile so having a similar alternative wouldn't be bad.

  • source
  • hideshow 9 child comments
  • [–] 2 points 3 months ago (8 children)

    Yeah it never really works for me either. I mostly only use it for access to my uploaded files, but even for that it hardly works.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 4 points 3 months ago (7 children)

    On the normal lemmy UI, there's a tab on the profile page that lets you see and delete uploaded images.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 3 months ago (6 children)

    The normal Lemmy UI will not load for me on Safari on iOS or macOS and I have been instructed to use photon, which mostly does not load as well.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 3 months ago* (last edited 3 months ago)

    Ah, darn. Unfortunately I don't have any apple devices to test, but does it load okay in a non-safari browser like firefox on MacOS? I'm guessing you're kinda screwed on iOS since from what I recall, alternative browsers there are just Safari re-skins :(

    I'll try to see if Blorp has any upload management ability and report back, since that's available on both iOS and Android.

    Update: Blorp does not. At least, not the mobile app :(

  • source
  • parent
  • [–] [S] 3 points 3 months ago (4 children)

    If that was caused by Anubis, maybe try again now as currently we use only Iocaine on the normal UI?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 3 months ago* (last edited 3 months ago) (3 children)

    So far, without Anubis, everything is loading correctly with the default webUI. Hopefully iocaine works at keeping out the bots.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 4 points 3 months ago* (2 children)

    Technically it is worse at it than Anubis and probably needs some additional scraper block like hapdash behind it to weed out the residential proxies that have become common, but for some reason Anubis was causing some scraper to go into some sort of reconnection loop and that heavily taxed our reverse-proxy. With Iocaine it seems to just happily ingest the LLM poison and that causes much less load on our server, so for now that solved the issue.

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

    The problem I was having with Anubis was every link I clicked checked I was legit and after two or three the page html(?) stopped fully loading and I had a mess of a view. On my Mac I can force reload to purge my cache, but on iOS I have to clear my entire browsing history each time, and it only lasted a few clicks before I had to do it again.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 3 months ago

    I previously noticed similar behaviour on the mlmym client specifically, but otherwise never came across it. I really have no idea in what way Safari might break the Anubis check, but given that this is not a common complaint by Mac users it seems something very specific to your setup.

  • source
  • parent
  • [–] 2 points 3 months ago

    Blorp works very well.

  • source