[Standards] Re: compliance levels for 2008

Nathan Fritz nathanfritz at gmail.com
Thu May 10 19:35:44 UTC 2007

> One point against having MUC as a requirement is that MUC can be
> federated out. users on hawkesnest.net can access MUC at
> conference.jabber.org. So the implemented services of hawkesnest.net
> arguably include MUC, regardless of whether it's a part of that server.
>   This is distinct from a mere plugin like starttls.

This is exactly the reason why it makes sense to have MUC as a client
feature and not as a server.  Just because your server doesn't support MUC
doesn't mean that you can't use conference.jabber.org or any other MUC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070510/5446036e/attachment.html>

More information about the Standards mailing list