We now have mlmym, Alexandrite, Voyager, and Photon frontends :) (lemmy.fmhy.net)

submitted 1 year ago* (last edited 1 year ago) by nullishcat@lemmy.fmhy.net to c/freemediaheckyeah@lemmy.fmhy.net

23 comments fedilink hide all child comments

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

Cloudflare charging $10 to have layered subdomains

...it's because CF wants money for that and I'm not paying for that shit lmao

top 23 comments

sorted by: hot top controversial new old

[-] russjr08@outpost.zeuslink.net 3 points 1 year ago

I feel you on the subdomain level/nesting restriction from CF, definitely made me go 🙄 when I first encountered it...

[-] Caligvla@lemmy.dbzer0.com 3 points 1 year ago

Doesn't look like the mlmym frontend is working for other instances beside fmhy.net.

[-] nullishcat@lemmy.fmhy.net 2 points 1 year ago

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

[-] tustamido@lemmy.fmhy.net 3 points 1 year ago* (last edited 1 year ago)

Thank you!

Maybe you should promote these links in main page sidebar like other instances do for people to notice them.

[-] nullishcat@lemmy.fmhy.net 1 points 1 year ago

Maybe. I don't really like promoting stuff in the sidebar, especially since rn there's no links there, but maybe in the future.

[-] Martineski@lemmy.fmhy.net 1 points 1 year ago

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.

[-] tustamido@lemmy.fmhy.net 2 points 1 year ago

There's something wrong in fetching thumbnails for old-lemmy.

old-lemmy.fmhy.net: https://i.imgur.com/t8OPh7e.png
old.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:

[-] nullishcat@lemmy.fmhy.net 2 points 1 year ago

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.

[-] tustamido@lemmy.fmhy.net 1 points 1 year ago* (last edited 1 year ago)

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.

[-] nullishcat@lemmy.fmhy.net 1 points 1 year ago

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.

[-] CommunityLinkFixer@lemmings.world 1 points 1 year ago

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

[-] Martineski@lemmy.fmhy.net 2 points 1 year ago* (last edited 1 year ago)

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.

[-] nullishcat@lemmy.fmhy.net 5 points 1 year ago

yeah it looks better but i am NOTTTT paying $10/mo for that

[-] Martineski@lemmy.fmhy.net 3 points 1 year ago

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.

[-] nullishcat@lemmy.fmhy.net 5 points 1 year ago* (last edited 1 year ago)

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.com and *.example.com. These cover everything from example.com to superlongsubdomain.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!!)