- old-lemmy.fmhy.net - mlmym frontend
- a-lemmy.fmhy.net - Alexandrite frontend
- m-lemmy.fmhy.net - Voyager frontend
- p-lemmy.fmhy.net - Photon frontend
If you don’t like the layout of regular Lemmy, feel free to use these :) (They can also be used for instances other than ours. Except for mlmym, they only have a single instance mode and no default instance config)
And in case you’re wondering why we aren’t using old.lemmy, a.lemmy etc instead…
…it’s because CF wants money for that and I’m not paying for that shit lmao
There’s something wrong in fetching thumbnails for old-lemmy.
old-lemmy.fmhy.net: https://i.imgur.com/t8OPh7e.pngold.lemmy.zip: https://i.imgur.com/vuSwxiD.pngAh, I just noticed this issue isn’t restricted to mlmym frontend… So it’s something affecting Lemmy FMHY instance as a whole.
Example:
after switching to ansible, pictrs (the image backend) didn’t have proper perms to access its own folder (for whatever reason.) this is now fixed.
Thanks. Other thing I noticed is FMHY is failing to federate with Hexbear, one of the most active instances. Compare:
Some instances don’t like to federate with them, but I see Hexbear linked with FMHY, so I guess there’s something wrong.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !news@hexbear.net
I know. I’ve been trying to fix federation over the past week and unfortunately it hasn’t been working. See this GH issue and this Maintanence Notice.