!freemediaheckyeah@lemmy.dbzer0.com 🤐

I'd like to apologize to everyone for doing this on such short notice and not being able to get it stable. It's been a fun ride but it's clear that it ended a long time ago. I'll see you all on db0.

Some more specifics:

• The instance will lock registration and community creation on October 1st. There doesn't seem to be a way to disable posts and comments rn so ig it'll be left on. I'll be keeping the instance up for the foreseeable future for archival reasons.
• Frontends will be kept up.

We started running an Uptime Kuma instance on M4D's servers. I'll post any status notices there.

We started running an Uptime Kuma instance on M4D's servers. I'll post any status notices there.

See my above comment about this. (Also what instances even allow piracy? And which ones aren't already blocked by everyone else, or would be trustworthy enough to not ban FMHY?)

Ah, I thought you were suggesting another platform like Lemmy and Divolt. For announcements I'm thinking of adding a simple status page hosted on GH pages or on the server this is running on (but I'm waiting on the other staff members for their thoughts.) For wiki updates, Reddit still exists.

The biggest problem with having other platforms is:

1. Another platform we have to maintain and manage
2. Needs to be non-bannable (so no twitter/x, discord, so on)
3. Needs to be at least usable (which is why divolt was chosen over matrix and IRC, and will prevent usability issues that we've had with firefish and lemmy)

If you can suggest a good platform that meets the last two, then maybe. But it's pretty unlikely we'll have another one. (I mean, Lemmy itself is already having problems and I'm pretty much the only person on it now, adding another platform isn't gonna help with that.)

kbin has always had problems with Lemmy federation and thus I'll be focusing on other problems. See https://github.com/LemmyNet/lemmy/issues/3876

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.

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.

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!!)

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