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.

Something like: <unique-stable-uuid id="7246ccd2-783b-4841-39a5-7b2b224f7eda"/>

Or in the case of server interference: <unique-stable-uuid 
id="5ed652a5-22f2-4878-08ad-48a2d3ac9978" spoofed="true"/>

Simple 😄


The informational guidance XEP is a good idea too.

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to