[Standards] Blocking command and Privacy Lists

Holger Weiß holger at zedat.fu-berlin.de
Mon Dec 22 21:22:28 UTC 2014


* Dave Cridland <dave at cridland.net> [2014-12-22 16:31]:
> On 22 December 2014 at 14:47, Holger Weiß <holger at zedat.fu-berlin.de> wrote:
> > * Kurt Zeilenga <kurt.zeilenga at isode.com> [2014-12-22 05:31]:
> > > I think if anything in XEP 191 needs to change, it's the discussion of
> > > how one maps XEP 191 onto XEP 4 privacy lists that should change.  It
> > > should be clearly stated that the blocking entity is required to perform
> > > the mapping in such a way that all communications with the blocked JID
> > > are blocked.
> >
> > And how should that entity map privacy rules that just block _some_ of
> > the communication back to XEP-0191 rules?
>
> XEP-0191 maps to XEP-0016, not the other way around.

XEP-0191 says it should work in both directions:

| If one of a user's clients uses privacy lists instead of blocklists and
| modifies the default privacy list by removing a blocked JID or blocking
| a new JID, then that change will be reflected in the blocklist.
|
| [...]
|
| If one of a user's clients removes the default privacy list and
| substitutes a new list for the old list, the blocked JIDs in the new
| default privacy list (if any) will become the new blocklist.

[ http://xmpp.org/extensions/xep-0191.html#privacy ]

Holger



More information about the Standards mailing list