Am Fr., 23. Okt. 2020 um 15:06 Uhr schrieb Tedd Sterr <[email protected]>:
> For the message method, I expect what happened was that at least one popular > client, rather than leave the body empty, inserted the content of the url > element into the body, and then others did the same, so now that has become a > de facto requirement. While inserting the url into the body isn't wrong, it's > obviously not the intention of the XEP - it does include separate body, url, > and desc elements for a reason - so requiring it be that way is wrong. FWIW at least one popular client will happily accept messages with an x-oob URL and *no* body. What it (currently) won’t accept is 'mixed' content with body != x-oob. As far as discovery is concerned there is not just "the MUC issue" but also offline clients and multi client setups in general. cheers Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
