On Wed, 22 Feb 2023 at 13:33, Thilo Molitor <th...@eightysoft.de> wrote:
> > There is a very obvious solution to this which everyone seems to be > > overlooking: we need a new element with a guaranteed unique, non-spoofed > > UUID; should a server feel the need to do bad things, it can set the > > 'spoofed' attribute to true and then clients can act accordingly. > what entity would set that element? the sending client? the server of that > client? the server of the receiving client? Any entity that's doing Bad Things of course. See also XEP-0076, RFC 3514. Dave.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
