I was made moderator of the /c/TrueAnon on the lemmy.ml instance a while ago, and none of my actions have ever federated to lemmy.ml, so I gave up. Thought I’d try again after this upgrade and still no dice. The response I’m getting back from the API when I try to add my lemmy.ml account to moderator status is “not_a_moderator.” Is this a transient federation issue or are there more fixes required for this scenario to work correctly?
I’m seeing the same behavior before and after 0.18.5. I have a second account on the instance of the community I moderate for this exact reason.
And that basically confirms that it’s a remaining problem with admin accounts taking remote mod actions. l suppose in the mean time I’ll try to have an admin at lemmy.ml give my @bilb@lemmy.ml account moderator status as a workaround. The other original moderator who could do it isn’t very active.
I couldn’t find an open bug ticket for this on Github, but that doesn’t mean there isn’t one. I’ll take another look and report it if I still can’t find anything.
Is this confirmed now? (link to the issue) I was about to make a thread if the issue is fixed and both instances I have accounts on are on 0.18.5 I could give my main account the moderator status and remove my workaround account.
I found an easy workaround. Just be a. mod for a community without any traffic.
