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