this post was submitted on 01 Sep 2023
5 points (85.7% liked)

FREEMEDIAHECKYEAH

644 readers
1 users here now

๐Ÿดโ€โ˜ ๏ธ Wiki / ๐Ÿ’ฌ Chat

founded 1 year ago
MODERATORS
[email protected]
[email protected]
5
We now have mlmym, Alexandrite, Voyager, and Photon frontends :) (lemmy.fmhy.net)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
10 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 10 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 2 points 1 year ago (1 children)

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

Ah, I just noticed this issue isn't restricted to mlmym frontend... So it's something affecting Lemmy FMHY instance as a whole.

Example:

[โ€“] [email protected] 2 points 1 year ago (1 children)

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.

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[โ€“] [email protected] 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.

[โ€“] [email protected] 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: [email protected]

[โ€“] [email protected] 1 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.

[โ€“] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[โ€“] [email protected] 1 points 1 year ago (1 children)

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

[โ€“] [email protected] 0 points 1 year ago (1 children)

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.

[โ€“] [email protected] 1 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!!)