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.
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.
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.
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.