File

mod_pubsub, mod_pep: Support per-node configurable inclusion of publisher This matches ejabberd's behaviour, using the 'pubsub#itemreply' config option. Although the current definition of this option in the specification is not as clear as it could be, I think matching what existing deployments do is the best option to resolve the ambiguity and reduce fragmentation. We should update the spec to be clearer about how to use and interpret this option. The 'expose_publisher' option for mod_pubsub is now an override (always expose or never expose). If unset, it will use the per-node config (which defaults to not exposing). Thanks to Link Mauve, edhelas and goffi for sparking this feature.

+
−
+
−This file documents the structure of the roster object.
+
−
+
−table roster {
+
−  [string bare_jid] = roster_item
+
−}
+
−
+
−table roster_item {
+
−  string subscription = "none" | "to" | "from" | "both"
+
−  string name = Opaque string set by client. (optional)
+
−  set groups = a set of opaque strings set by the client
+
−  boolean ask = nil | "subscribe" - a value of true indicates subscription is pending
+
−}
+
−
+
−The roster is available as
+
− hosts[host].sessions[username].roster
+
−and a copy is made to session.roster for all sessions.
+
−
+
−All modifications to a roster should be done through the rostermanager.