Looking for Potential Mods
Looking for Potential Mods
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.
You're viewing part of a thread.
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.
Hello @[email protected] ,
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)
No worries, thanks for chiming in
resolving reports doesn’t actually federate, which is quite annoying
Seems to reflect my experience as well.
@[email protected], it looks like qaz and I both agree on this point?
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.
Glad to see we agree in the end!
Honestly, I appreciate the effort you put into looking into it, but we could've saved a lot of effort and time if you had looked at the modlog like I suggested 3 weeks ago. Or, idk, trusted that I wasn't lying to you?? Or, I know you have like 4 alts, too, so you also could have just tested it yourself before spreading misinfo to new mods.
It wasn't harmful misinfo, but it's misinfo nonetheless and I'm not gonna lie, it's annoying that it took this much work to correct you. Especially after your antagonistic behavior in the past. And especially especially after I've already demonstrated to you that the problem as you presented it was wrong, and (if Martineski wasn't mistaken) at least one other person also told you you were wrong.
I agree with Martineski: Going forward, accurately convey the problem and inform people that it'll be fixed in Lemmy v1.
this much work to correct you.
Wait, what? Are we supposed to start the whole discussion again?
- the consensus is to use local alts to mods. LW admins recommend that, the Lemmy devs recommend that, the people who opened the tickets on the GitHub recommend that, other instances admins recommend that.
- you think that it's not the case because qaz made some testing but you are not sure what, and you assume that because you can resolve reports from another account it works.
- I stand by the fact that the consensus is to use local accounts.
- we go into the long discussion, you try to point me out that I'm wrong, I investigate and ping qaz
- qaz confirms that the resolving reports don't federate, meaning that using local accounts to resolve reports is the recommendation.
at the modlog like I suggested 3 weeks ago
Why would I look at the modlog when everyone involved on this topic agrees that using local accounts is the recommendation to mod from local accounts?
trusted that I wasn’t lying to you?
I didn't say you were lying, I was saying that you were not following the recommendation that is to use local accounts to mod. You still don't, by the way, for both this community and [email protected].
and (if Martineski wasn’t mistaken) at least one other person also told you you were wrong.
The other person is you.
antagonistic behavior
I was getting antagonistic because it was the straw that broke the camel's back. That you mods were power tripping by wanting to move !196 to lemmy.world against the community's will was already bad, but then when you confessed you didn't even have a local account, (and that hence your handling of the reports would not federate to LBZ), that was the just too much.
It's okay to make mistakes, but it's usually better to recognize them.
Anyway, long live [email protected]
The issue as you were presenting it was just wrong. Plain and simple. If you're not going to own it, that's your prerogative.
Me and Qaz both have told you now that having a local account doesn't solve the issue. You need several alts, local and remote.
Me and Qaz both have told you now that having a local account doesn’t solve the issue. You need several alts, local and remote.
Let's give it another go then.
If you are the only mod team in the entirety of Lemmy who use a specific alt to get more reports, this should be raised, and all mod teams should have that specific set of mods.
I just had a look at the
- https://lemmy.ml/c/lemmy: only local mods
- https://lemmy.world/c/technology: only local mods
- https://lemmy.world/c/news: only local mods
- https://lemmy.world/c/world: only local mods
- https://lemmy.ml/c/asklemmy: only local mods
All of those LW communities are probably the one with the most reports as they are the most active of the whole platform. None of those team use remote accounts to mod.
There may be something strange happening with the LBJ setup (potentially due to the high number of users and instances banned). Let's hope qaz can detail more when they have more time.
That whole issue does not change anything to the fact that for the report resolve to actually work, you need to use a local account as remote accounts don't federate.
Be aware that
the reports don't federate, so people modding from non local accounts won't get reports.the usual recommendation is to use local accounts do moderate, as remote accounts resolves of reports do not federate to the community host instance.I edited my comment for completeness, but it does not change the key message: it is recommended to use local accounts to be able to perform all mod actions (while we wait for qaz detailed explanation). The reasons behind doesn't change anything to the recommendation.
Also, following your own logic, you have directly asked the mod of this community to add your lemm.ee account as a mod to catch all the reports rather than just suggesting it as an afterthought. But it seems like you're only using this argument as an excuse to defend why you were not wrong by wanting to mod from a LW account.
They can recommend whatever they want. Doesn't change the fact that local alts have the same issue, and you need several.
I'm not making any argument other than to counter your claim that reports don't federate at all. That's misinformation. Which you seem to understand now, so why you're still arguing is beyond me.
@[email protected], as you reported https://github.com/LemmyNet/lemmy/issues/4701 , could you please tell if there any known occurrences of local moderators not getting reports for local communities?
You can read the thread above for details.
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.
Hello,
Thank you for chiming in.
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?
Anyway, not that critical.
if an instance can't see a post, e.g. due to the creator being banned or the instance being defederated, it can't receive reports for those posts either.
a post by an exploding heads user in a blahaj community will typically not federate to any other instances on its own, as the community instance would have to announce the post to other instances. there are some flaws in this where e.g. manually resolving the post from another instance will federate it, as well as mentioning someone on another instance from a comment.
with the recent changes not yet in a 0.19 release, reports will also go to instances that have moderators other than the community instance. that could potentially also trigger federation of the content itself to those instances i think and it would bypass the need of the community instance not having the instance blocked. ideally defederated instances would not be able to post to those communities in the first place, but that's tricky to implement.
I'm not even talking about LBZ or !196
If all reports don't make it to local mods, then that's an issue that's impacting the whole platform, hundreds of communities.
I'm to reread the thread when Moss and Ada explained their versions of the issue, because this doesn't seem right.