If you silence somebody, it should be remembered and persisted. And there is no "muted" affiliation.
From XEP-0045:
> An implementation MAY persist roles across visits and SHOULD do so for moderated rooms (since the distinction between
visitor and participant is critical to the functioning of a moderated room).
MattJ
on
I think we should do this, but only for users with an affiliation to start with. It shouldn't be too hard. This would be useful for GC3 (where some GC3 stuff is planned to map to affiliation+role combinations for backwards compatibility with MUC).
Later, we can optionally add some kind of cache of time-limited role assignments for unaffiliated JIDs if we want to handle the "mute unaffiliated user" use case.
If you silence somebody, it should be remembered and persisted. And there is no "muted" affiliation. From XEP-0045: > An implementation MAY persist roles across visits and SHOULD do so for moderated rooms (since the distinction between visitor and participant is critical to the functioning of a moderated room).
I think we should do this, but only for users with an affiliation to start with. It shouldn't be too hard. This would be useful for GC3 (where some GC3 stuff is planned to map to affiliation+role combinations for backwards compatibility with MUC). Later, we can optionally add some kind of cache of time-limited role assignments for unaffiliated JIDs if we want to handle the "mute unaffiliated user" use case.