> 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. The XEP clearly explicitly allows them to be different - indeed, it's expected they are different - so if an implementation breaks as a result of that, that's very much an implementation problem.
> As far as discovery is concerned there is not just "the MUC issue" but > also offline clients and multi client setups in general. True, but these are the same reasons holding back so many other things - everything is broken, let's do nothing just in case.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
