You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With various combinations of the blinded setting, older Session dev
versions, and the cli tool, you could end up with a "stuck" unblinded
moderator that can't be removed (when blinding is enabled) because the
blinded ID already exists, so when you try to remove it it removes
moderator status from the *blinded* user instead.
The resolves a few things around this:
- the cli tool now tries to remove *both* the blinded and unblinded
mod/admin permissions if given an unblinded ID with a known blinded
ID, to "unstick" this moderator.
- the cli tool was wrongly showing the given session id, rather than the
actual resolved session id, so was showing that it was removing
"05..." when actually it was removing the blinded user "15...".
- legacy endpoints for adding a moderator (and bans) now try blinding
the ID. This hopefully won't matter as I don't believe the legacy
endpoints will get used with the updated Session client, but might
make a difference if blinding gets flipped on and then off again.
0 commit comments