I have been helping with two channels to get PL50 and both times it has been helped to op the ghost again.
Now I saw a third case of this reported, so I think it's not only me.
Just got stripped of power level 50 when I received operator status in a channel.
I looked around the source a bit, and it looks like it's an inconsistency in the irc module's internal state, since the appservice assigns power levels according to a user's prefixes (e.g. @).
I don't see why doing it twice is needed. It's likely a state bug in node-irc. Probably related to https://github.com/matrix-org/matrix-appservice-irc/issues/380
Notably, on moznet, the IRCd deduplicates modes and suppresses no-op mode changes. As a result, the workaround is impossible to perform, and moznet cannot bridge +o across at all.
In light of this, can this bug be prioritized?
(Paraphrase of my message to #irc:matrix.org)
Hey, Mozilla is apparently planning to spin down irc.mozilla.org (timescale unspecified; source: http://exple.tive.org/blarg/2019/04/26/synchronous-text/), and I was hoping to double-bridge the Matrix side of a couple of rooms I'm friends with the owner of as part of a migration path to another server. I'd already commented here about this, but with the latest news, this has become a bit more pressing.
This issue seems to affect mode syncing in general as +m needs to be reverted by running /mode #channel -m a few times for it to sync to Matrix.
https://matrix.to/#/!BAXLHOFjvDKUeLafmO:matrix.org/$U+lk1qP+c4zmzomWRp4EAS0VPsB9NCKKE7siZ4rSV9o?via=matrix.org&via=chat.weho.st&via=disroot.org
Most helpful comment
Notably, on moznet, the IRCd deduplicates modes and suppresses no-op mode changes. As a result, the workaround is impossible to perform, and moznet cannot bridge +o across at all.
In light of this, can this bug be prioritized?