EDIT: Trying it again today, hoping it will work out before tonight when my old instance goes down. So far, it very much looks like yesterday is repeating itself. My personal guess is, the mod promotion doesn't properly reach lemmy.world for some reason, and then later, the other two instances sync with lemmy.world as the authority (after all the community is on there) and say (rightfully) "hey, the instance the comm is on doesn't have those accounts as mods, we better remove the privileges again!".

lemmy.abnormalbeings.space sees:

lemmy.world sees:

piefed.world sees:

So, my original instance lemmy.abnormalbeings.space will be closing down tomorrow (as of this post) due to lack of use and overall a re-focussing on the PeerTube platform on the server. Originally, !peertube@lemmy.world was created by someone else, but they seem to have deleted their account on lemmy.world and moved over to piefed.social. So my account is currently the only mod left.

As my old account on my instance, I added my new accounts (on PieFed.world and Lemmy.world respectively) as moderators, and locally on my instance, they appeared in the interface immediately (at first). My PieFed account also appeared as a moderator a short while after on PieFed.world in the interface. Thinking this might just be a federation issue for the lemmy.world account to also be added, I let it sit for a few hours, but unfortunately, now neither of the accounts appear as mods any more (also on my old instance), seemingly something in the federating process removed them again, or something in the system rejected the promotion (maybe because the accounts were too young?).

This is not ideal, since after my self-hosted instance will go down, there would be no moderator accounts left for the community. Does anyone know what could be the issue and how it could be resolved?