As the title says, I'm looking for some potential mods to help run this community.
If you are interested, are a current mod of the QDL Subreddit, etc., then drop a comment to this post explaining why you believe that you would be a good fit for mod.
Report federation used to work. I appointed several mods from other instances back then. The issue seemed to have appeared in May 2024 (https://github.com/LemmyNet/lemmy/issues/4701).
I don't want to go through the update timelines of LW and LBZ, but on [email protected], LW admins still state that
Note that, due to a bug in Lemmy, you will not be able to see reports in the community since your account is on a different instance. You could work around it by making a lemmy.world account just for moderating.
I had a look at the modlog, it works in this case indeed ( https://lemmy.blahaj.zone/modlog/2942?page=1&actionType=All&modId=115895 ). I am not saying it never works. I am saying that there are known cases where it does not, which is why the LW admins recommend people to use local accounts. Maybe in this case it's because the report was from a LBJ account for a LBJ community?
I also posted about in 19 days ago on [email protected]: https://lemmy.world/post/24576402 . Other mods and admins reported other actions that would not federate. Nobody contradicted the fact that it could be working sometimes.
The consensus recommendation is just to use local accounts while we wait for the fix to be released. It's just easier than to try to figure out what works and what does not, in which conditions, etc.
There are federation issues with reports, but it's not as simple as you've been saying, and having a local account doesn't solve it. There's a reason Qaz has several alts modded at 196 outside of LBZ. He needs them because there are several reports that don't federate with LBZ, LW, or lemm.ee.
There’s a reason Qaz has several alts modded at 196 outside of LBZ. He needs them because there are several reports that don’t federate with LBZ, LW, or lemm.ee.
So mods who don't have that specific set of alts don't see all reports? That should probably be raised to all the mods of the platform, as your team seems to be the only one aware of that issue.
IIRC Qaz has mentioned it in the LBZ mod channel in Matrix at least once. If they didn't hear it from him, it should be obvious something's up when Ada tells them there are unresolved reports and their mod queue is empty.
If you feel it should be shouted from the rooftops, then nobody is stopping you.
Could you please provide some details on why you need all of the alts to mod [email protected] ?
Seems like there are several reports that don’t federate with LBZ, LW, or lemm.ee.
That's a an issue that does not seems well know (as stated in the comments above, the general recommendation from the LW admins is to use a local account).
Some other AP platforms such as Kbin have many issues with federating reports and even bans / content removals. Some Lemmy instances don't federate reports due to defederation and some don't federate due to reasons that are still unknown. It's even possible for the community's host instance to not get any reports in some cases. It has happened before that after adding an alt, 80+ reports became visible that weren't visible from any other instance.
All in all, federation related to modding still feels really spotty and I often encounter weird problems, such as vanishing / inconsistent modlogs, reports not resolving (resolving reports doesn't actually federate, which is quite annoying), and plethora of other issues. It seems that so far the Lemmy devs have bren busy with other things and thus mods have had to learn to deal with it with various scripts and bots.
I have been planning on making a post discussing this, but I'm waiting for the problematic posts and images to be removed first.
(Also I have to go soon so I didn't have time to read the full discussion)
Yeah I actually had no idea that resolving reports didn't federate either. The situation is definately worse than I thought, but hopefully they'll fix it soon. Thank you (and Qaz) for looking into it.
I'm not aware of any cases of reports not reaching the community instance other than "generic" federation issues that could happen from misconfiguration or some random issues, but generally since 0.19 and the persistent federation queue it should be quite reliable. before that there was no retry logic if an activity failed to send and it was just discarded.
I'm not entirely sure on the behavior on banned users though, if the reporter is instance banned it'll probably ignore their report. other than that I can't think of anything right now.
if the reporter is instance banned it’ll probably ignore their report
There is also an edge case when someone from let's say exploding-heads reports another user from exploding-heads (which is not federated with Blahaj). Blahaj probably wouldn't get the reports, but someone on lemmy.sdf.org would, as they don't defederated exploding-heads?