On 2019/07/17, Jonas Schäfer wrote: > On Montag, 15. Juli 2019 17:57:12 CEST Jonas Schäfer wrote: > > The XMPP Extensions Editor has received a proposal for a new XEP. > > > > Title: Anonymous unique occupant identifiers for MUCs > > Abstract: > > This specification defines a method that allows clients to identify a > > MUC participant across reconnects and renames. It thus prevents > > impersonification of anonymous users. > > > > URL: https://xmpp.org/extensions/inbox/occupant-id.html > > (Council Hat) I am +1 on this. > > I think this should be supported in all modes of operation of MUC, no matter > the anonymity. It helps with things like Message Correction as someone else > has already pointed out.
It doesn't especially help with Message Correction in non-anon MUCs, as you can track the identity with the real jid. I also want this anyway, if only to be able to unify the way things are handled. > As to the concern raised by someone about admin tasks: Moderation tasks > should > of course be able to use the occupant-id (future work). Regarding actual > server administration tasks, server admins surely have a way to reveal the > true JID of anyone connected to any MUC on their server, so they can still > ban > the entire domain. The MUC service could also expose such a feature for full- > anon rooms, via Ad-Hoc command or similar, to room owners. I can definitely get behind this. -- Maxime “pep” Buquet
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
