Federated-Community-Mod losing mod status

[pixlguru]

Issue Summary

Sometime after appointing someone as a mod for a federated community, the mod loses mod-status

Steps to Reproduce

1. appoint a local user as a mod for a federated community
2. After a day or so, the mod disappears from the modlist

[dessalines]

mod for a federated community

Who is appointing that mod? An admin, or another federated mod?

[pixlguru]

Who is appointing that mod? An admin, or another federated mod?

An admin is appointing that mod.

[dessalines]

That's definitely working correctly then, an admin should not be able to appoint mods for communities that don't live on their instance. Not showing that ability is probably a UI issue.

[pixlguru]

The UI even asks "are you sure yes/no", but just in that case, don't know why.

If I appoint a local user as a remote community mod, right now the mod is listed only in the modlist on my own instance. I'd like that feature to be honest, would make admins life of moderating much easier, so if it is not a bug consider it a feature request ; )

[dessalines]

An admin of one instance shouldn't have power over a community that lives on another instance tho. Otherwise I could just make an instance, and control every community in the lemmyverse. But yes I agree its a UI issue to not show that.

[pixlguru]

An admin of one instance shouldn't have power over a community that lives on another instance tho. Otherwise I could just make an instance, and control every community in the lemmyverse.

But that wasn't the case, the mods actions had no affect on the federated instance, so neither the admin nor the mod has control over the remote instance. It was just working like local moderation for a remote comm.

[kromonos]

I also already thought about a “Local Global Mod” as a role. The role could support the administrator with local moderation over all local communities, without the need of granting the full admin role.

[dessalines]

But that wasn't the case, the mods actions had no affect on the federated instance, so neither the admin nor the mod has control over the remote instance. It was just working like local moderation for a remote comm.

How isn't that the case? You are trying to appoint mods for a community you don't control, and this issue is about those mods not federating to the host community.

[pixlguru]

probably i didn't explain it well enough, the issue is not that mods are not federated. So all modding should only affect the local instance, deletes, bans etc., as any admin can do already on federated content on his own instance. i just want to allow mods to do the same on appointed fed communities.

This works already, the mod only shows up at the local instance modlist, not on the federated modlist. actions are only affecting the local instance, no issue here.

the issue is just that the local mod drops out of my local modlist of that comm after some time.

i hope this could explain it a bit better...

[pixlguru]

It's rather related to https://github.com/LemmyNet/lemmy/issues/2071 but not site-wide but on community basis

[dessalines]

I think its good that local admins have control over content federated to their servers, but I heavily disagree with allowing separate "local modlists" for federated communities.

[kromonos]

I think its good that local admins have control over content federated to their servers, but I heavily disagree with allowing separate "local modlists" for federated communities.

I think it's more like the mod can only moderate the local content that was federated. Not the entire remote community. E.G. remove federated spam, which was not removed, even if it was removed on the original community.