In article <[EMAIL PROTECTED]>, Stephen Marquard <[EMAIL PROTECTED]> wrote:
> Daniel Henninger wrote: > > Hi folk, I had sent this to the jadmin list and just realized it's more of > > a jdev question. > ... > > > > I'm afraid I'm not understanding how to implement this properly. First of > > all, I'm running a Jabberd 2.0s4 server. Is JEP-0126 implemented as of > > that version? Second, looking over the JEP is making me question how it > > would be used properly. Take the various transports. (more precisely, > > I'm looking to implement invisibility with PyICQ-t) Unless I'm reading > > something wrong, it looks to me that the client/user would have to know to > > grant visibility "rights" to the various transports he or she is > > subscribed to. If this is truly the case, it more or less renders > > invisibility in transports useless. I doubt it is going to occur to many > > to grant said access. Am I simply missing something or is there another > > way around this for transports? Thanks!! > > jabberd2 implements privacy lists as defined in XMPP-IM, as well as > legacy "invisible presence". JEP-0126 describes how to use privacy lists > in XMPP-IM to implement invisibility, so in that sense jabberd2 > implements it, though most of the work to use privacy lists in a useful > way is on the client side. Yes, this is something that the client needs to be smart about -- certainly one would not expect the user to make all those changes manually. Peter _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
