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)
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:
- Another platform we have to maintain and manage
- Needs to be non-bannable (so no twitter/x, discord, so on)
- 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
After a full week of trying to fix this and a few days of running with multiple patches, it seems as though there are still problems with federation. So I'm resorting to crowd sourcing: if you notice any problems interacting with other instances (voting, commenting, posting), or you're from another one and can't interact with FMHY, make a comment here. Include two links: one on the side without any issues, and one with them (if possible.)
Example post: New communities may not federate properly.
This will hopefully pinpoint what instances and/or types of activities are causing problems and why - are they using CF or not, are their servers just blocking us, is it specific to posts made on FMHY or does it include FMHY posts made on other instance's communities, stuff like that.
As for current workarounds:
- There is a userscript known as "LULS" (Lemmy URL Link Switcher) which mainly redirects all links (on other lemmy instances) to a configurable host instance. This script seems to do some funky stuff with federation, and sometimes manages to properly sync posts or communities when used. (Comments may not work after a post has synced.) If you're worried about safety, edit it to only allow usage on the domains you want.
- Try the regular federation process first. Some instances seem to behave differently to this (mostly lemmy.world during my tests), but searching does occasionally work properly.
I'd also, again, like to ask for anyone with technical knowledge on Lemmy. I'm now currently the only staff member on this and even though we don't have many people here anymore, it doesn't hurt to try or ask.
I'd also like to thank anyone for sticking around for this long, particularly u/Martineski and u/mr_MADAFAKA. Also thank you to dbzer0 for his help on this problem so far. Without everyone still here, we would've stopped running this instance, so thank you :)
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.
The server will be down from 18:00 UTC for possibly one hour (not sure how long exactly) to replace the current docker + compose setup with an ansible setup. This is to hopefully fix any current federation problems, and if not, then to at least eliminate any issues software wise.
On a related note - If you're a technowizard, especially when it comes to ActivityPub and Lemmy BE, please message me (either here, over email, Discord (nullishcat), Matrix (nullishcat:matrix.org), or Divolt.) I still do not know the root cause of this problem and have nearly exhausted all potential fixes (the remaining ones being this setup change and switching providers.)
Technical details can be found here: https://github.com/LemmyNet/lemmy/issues/3862#issuecomment-1711051012
EDIT: We're back up, very sorry for the long wait. (Ansible's setup guide is very poor and didn't make it clear that it needs to be run on a local PC running Linux/Mac and to copy the volumes to /srv/lemmy/volumes.) Federation tests will start shortly.
Unfortunately not for new communities. Are you able to see c/games, c/singularityai, or c/testcomm?
test test test
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:
- You're trying to upload a file larger than allowed (1MB)
- 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
- old-lemmy.fmhy.net - mlmym frontend
- a-lemmy.fmhy.net - Alexandrite frontend
- m-lemmy.fmhy.net - Voyager frontend
- p-lemmy.fmhy.net - Photon frontend
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