It was just a file permissions issue on my end after switching to Ansible, ran chmod -R a=rwx where pictrs was located. (This probably won’t help with db0.)

The old instance had its own problems (mainly pictrs not working) but its mainly because I was the only active sysadmin on this new instance. The old one had multiple and while I had some help from db0 and a few others, I was still essentially the only person maintaining it.

Thank you but money wouldn’t help. (Unless you had like $100 to hire a specialist and figure out the federation problems.) Not to mention the main reason for switching is the amount of people on db0 compared to here (and we both essentially did the same thing, mainly piracy focused)

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

Firefish seems to be more broken than Lemmy sadly

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.

I don’t know the actual limit, it might be larger. It’s not set and it’s whatever the default is, which said it’s 1MB according to search results.

It’s possibly one of two things:

1. You’re trying to upload a file larger than allowed (1MB)
2. The image service is fucking broken again

If it’s the latter then I’m not dealing with that cause holy fucking shit I nearly blew my brains out while trying to troubleshoot the downtime… go upload on imgbb or somewhere else if that’s the case

We get it, you’re a lolicon. Don’t try to hide it, we can all tell :)

Haven’t heard of this one before. Added :)

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

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