Submitted 1 week ago by remon@ani.social to support@lemmy.world
I’ve been appointed as a mod 3 times now.
The action shows up in the modlog straight away, but it always takes a couple of hours until it actually works. Then, serveral hours later it seems to just reverse itself.
I suspect it has to do with ongoing federation issues on the side of lemmus.org. All post from lemmy.world are delayed by about 12 hours on that instance.
Maybe the delayed federation somehow messes with the mod appointments?
The federation delay is a known issue. LW has recently upgraded to the newer version, so hopefully they’ll be able to enable parallel federation to resolve the issue for us.
As for the mod appointment issue, I believe you’re correct that it is related. Interesting that it reverses itself though. I’d have to dig into the code to figure out why that might be the case. 🤔
Interesting that it reverses itself though. I’d have to dig into the code to figure out why that might be the case. 🤔
The apointment definitely worked for a while. I actually ended up in a strange state where I had “moderator view” on my tabs, but when I clicked on it it said “no posts, subscribe to a community”. But maybe that’s just due to browser cache, dunno.
kersploosh@lemmy.world 1 week ago
This is a long-standing Lemmy bug related to the moderator not being on the same instance as the community. I added you as a new moderator.
You will encounter other similar bugs due to you being on a remote instance:
remon@ani.social 1 week ago
Thank you.
For now the community is small enough for me to check everything without reports. But I guess I’ll need .world account as a backup eventually.
pruwybn@discuss.tchncs.de 1 week ago
I thought this was supposed to have been fixed in version 19.6, is that not the case? From here:
I’m having the same issue as the only active mod of lemmy.world/c/communitytv
kersploosh@lemmy.world 1 week ago
This looks like an issue that has come and gone over time. A comment in #4865 says remote mods could make changes in 0.19.3 but there were problems in 0.19.4 and 0.19.5. Maybe it really was fixed in 0.19.6, but broke again in a later version? LW is now on version 0.19.9.
In the meantime, if you need help making changes to your community then let me know. I’m happy to help until the bug is truly fixed.