Re: Proposed XMPP Extension: Explicit Mentions
Maxime Buquet <[email protected]>
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <abDCAh_9hJidrIax@kea> |
On 2026/03/10, Daniel Gultsch wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: Explicit Mentions > Abstract: > This specification defines a way to explicitly mention a person or > groups of people. > > URL: https://xmpp.org/extensions/inbox/explicit-mentions.html > > The Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > _______________________________________________ > Standards mailing list -- [email protected] > To unsubscribe send an email to [email protected] Thanks for taking over and making this a thing :) A few notes/nits, - The jid attribute Same as singpolyma, I would settle on requiring occupant-id I think for all types of rooms, makes the whole thing simpler, and rooms without it are scarce nowadays (at least in places that matter). I also did include a note about this in implementation notes. > Anonymous unique occupant identifiers for MUCs (XEP-0421) [3] is being used to mention in Multi-User Chat (XEP-0045) [1] instead of a participant JID or a real JID. This allows us to have a common solution across MUC, and also to use a stable identifier, that is guaranteed to be unique per occupant (bare JID) and prevent usurpation. - The noping modifier To me the purpose of the spec is to make mentions explicit. Thus changing the status-quo and making the non-usage of this spec "not" a mention, which would make the modifier redundant and confusing (mentioning not to mention). This somewhat conflicts with implementation notes: > Implementations SHOULD also allow sending participants to talk about someone without having to mention them. Might be useful as a temporary measure but I certainly wouldn't want that to stick around. _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]