- 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
Doesn’t look like the mlmym frontend is working for other instances beside fmhy.net.
My bad, I forgot mlmym only has single instance mode. If I could, I’d just set fmhy to be the default instance. Updated OP
Thank you!
Maybe you should promote these links in main page sidebar like other instances do for people to notice them.
Maybe. I don’t really like promoting stuff in the sidebar, especially since rn there’s no links there, but maybe in the future.
I think it would be good to make a faq post with common questions/answers which would include links to other posts like defederation stance, alternative interfaces and such and then pin it +include it in the side bar. This way it would be visible and organised while having only one pinned post and only one link in the side bar. At least that’s the way I would do things if I was an admin but it’s up to you guys to decide what’s the most optimal thing to do.
I feel you on the subdomain level/nesting restriction from CF, definitely made me go 🙄 when I first encountered it…
Will you consider adding Photon?
Haven’t heard of this one before. Added :)
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.
yeah it looks better but i am NOTTTT paying $10/mo for that
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!!)
I love these so much, but are there any equivalents for Kbin?
For kbin I’ve had luck with userstyles/Stylus extension. They have a budding amount of themes available. I’ll link later when I’m on a PC
AFAIK no. And since this is a Lemmy instance and not a Kbin one I probably won’t put one on here
Yeah I didn’t think that would even be possible. Just wondering if any exist yet.
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:
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.
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
