- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
I’m cross-posting this to [email protected] in case Issue #2 below is symptomatic of a sync issue that the admins need to know about.
cross-posted from: https://sh.itjust.works/post/5452780
My main account is on sh.itjust.works, but I am a mod for some communities on lemmy.world.
Issue #1: A few weeks ago I learned that user reports do not federate between instances (Github issue #3781). Therefore I cannot see reports from the .world communities.
Issue #2: As a workaround for #1, I created an account on lemmy.world. From my sh.itjust.works account I made my lemmy.world account a mod in my communities. Unfortunately, it is not taking effect. See the attached image for one example. My lemmy.world account does not know that it is now a moderator account.
Is issue #2 simply a sync issue between the two instances? Or is something else happening?
Is issue #1 expected to be resolved in the near future?
As an additional data point, my lemm.ee account doesn’t show your .world account as mod there either.
https://lemm.ee/c/[email protected]
@[email protected] I just noticed I can now see both your accounts as mod from https://lemm.ee/c/[email protected]
Did you manage to fix this? What was it?
I asked one of the lemmy.world admins to manually give my .world account moderator rights in my communities. That did the trick.
Though now I found another weird bug. From my sh.itjust.works account I should be able to hit the “leave mod team” button in one of the .world communities and have that account no longer be a moderator. However, when I try it the change doesn’t stick, and my mod rights come back a few days later. I suppose I could ask the .world admins and have them manually remove that account, but at this point I’m out of energy to bother with it. I will just have two mod accounts for a while. Maybe the upcoming Lemmy 0.19 release will fix some of these quirks.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
Thanks bot, but this one was on purpose