- 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...
*removed externally hosted image*
...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.png
Ah, I just noticed this issue isn't restricted to mlmym frontend... So it's something affecting Lemmy FMHY instance as a whole.
Example:
- https://old.lemmy.zip/post/2631959
- https://old-lemmy.fmhy.net/post/615405
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:
- https://old-lemmy.fmhy.net/c/news@hexbear.net?sort=New&listingType=All (no new post this week)
- https://old.lemmy.zip/c/news@hexbear.net?sort=New&listingType=All (13 new posts in the last 24 horus)
Some instances don't like to federate with them, but I see Hexbear linked with FMHY, so I guess there's something wrong.
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.
Thank you!
Maybe you should promote these links in main page sidebar like other instances do for people to notice them.
Why use "-" instead of "." to separate the prefix?
The dot looks better imo, that's all.
Edit: lmfao, I should learn to actually read stuff before commenting.
I wouldn't too because I don't think that there's any technical reason to make the user pay for that. Or maybe there is, I'm not very tech savvy.
With how cloudflare is setup, there technically is, but it's also bullshit. Basically they have two certificates for SSL (which allows for https):
example.comand*.example.com. These cover everything fromexample.comtosuperlongsubdomain.example.com, but NOT, say,a.b.example.com. That would require something like*.b.example.com.This is kinda BS though, as certificates are pretty much free nowadays. I guess it saves on server load? But it's so minimal that there really is no reason to charge for it, especially not with a monthly subscription. ($120/yr for certs!!)
