Wouldn't you have the same problems with the actual messages that come
from the MUC, i.e., they would be blocked by the client? I am not
familiar with how block list work, but no matter where the invite comes
from, once the client joined the meeting, the client will need to
unblock the room.
Peter Saint-Andre wrote:
Michal 'vorner' Vaner wrote:
So just one last question - how does a client know, when to send direct
or usual presence?
Sends both?
Perhaps. Inviting people to rooms happens infrequently enough that it's
not a bandwidth issue. But it may be confusing for the
Ian Paterson wrote:
*Maybe* we need to consider addressing the valid reasons that Google
Talk feels it needs this policy, rather than handling the symptoms of
the policy? Can we solve the real problem? i.e. can we create enough
anti-spim protocols and/or infrastructure to make Google (and
Currently it is not possible to send room invitations directly from one
person to another. That is, the invitation must go through the room. See:
http://www.xmpp.org/extensions/xep-0045.html#invite
This can cause problems with deployments that use privacy lists to block
communications from
Michal 'vorner' Vaner wrote:
Hello
On Thu, Jul 19, 2007 at 02:27:51PM -0600, Peter Saint-Andre wrote:
Currently it is not possible to send room invitations directly from one
person to another. That is, the invitation must go through the room. See:
Hello,
On Thu, Jul 19, 2007 at 03:34:25PM -0600, Peter Saint-Andre wrote:
Michal 'vorner' Vaner wrote:
Hello
On Thu, Jul 19, 2007 at 02:27:51PM -0600, Peter Saint-Andre wrote:
Currently it is not possible to send room invitations directly from one
person to another. That is, the
Michal 'vorner' Vaner wrote:
Hello,
On Thu, Jul 19, 2007 at 03:34:25PM -0600, Peter Saint-Andre wrote:
Michal 'vorner' Vaner wrote:
Hello
On Thu, Jul 19, 2007 at 02:27:51PM -0600, Peter Saint-Andre wrote:
Currently it is not possible to send room invitations directly from one
person to
