Wed, 21 Jul 2021 23:02:25 +0200 mod_pep: Remove use of RLU cache when persist_items was set to false
Kim Alvefur <zash@zash.se> [Wed, 21 Jul 2021 23:02:25 +0200] rev 11726
mod_pep: Remove use of RLU cache when persist_items was set to false This behavior came from some confusion over the meaning of persist_items. The correct behavior is that items are only stored when it is set to true. When set to false, the service becomes a "pure" publish-subscribe service, where items are forgotten immediately after broadcasting.
Thu, 22 Jul 2021 21:01:11 +0200 util.pubsub: Fix behavior of persist_items disabled
Kim Alvefur <zash@zash.se> [Thu, 22 Jul 2021 21:01:11 +0200] rev 11725
util.pubsub: Fix behavior of persist_items disabled When set to 'false' there is no need for a persistence interface at all, since items are not persisted after being broadcast. Had started wondering if maybe the behavior was wrong, after reading parts of XEP-0060 that pointed in that direction. Some discussion of this can be found in logs of xmpp:xsf@muc.xmpp.org?join from around 2021-07-20 Thanks to Ralph for confirming.
Wed, 21 Jul 2021 23:35:08 +0200 mod_pubsub: Explicitly enable persistence by default to preserve behavior
Kim Alvefur <zash@zash.se> [Wed, 21 Jul 2021 23:35:08 +0200] rev 11724
mod_pubsub: Explicitly enable persistence by default to preserve behavior Since nodes were always persistent according to the XEP-0060 definition. Whether data is stored in memory or on disk was not what this setting was meant for.
Wed, 21 Jul 2021 21:22:17 +0200 util.pubsub: Handle absence of node data interface
Kim Alvefur <zash@zash.se> [Wed, 21 Jul 2021 21:22:17 +0200] rev 11723
util.pubsub: Handle absence of node data interface This is in preparation for fixing the behavior of 'persist_items', which was misunderstood at some point. In mod_pep it toggles between persistent storage and in-memory storage, while the correct behavior would be to toggle whether published items are stored at all or forgotten after being broadcast.
Sun, 25 Jul 2021 14:23:35 +0200 mod_pubsub: Remove publisher field when not exposing publisher
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 14:23:35 +0200] rev 11722
mod_pubsub: Remove publisher field when not exposing publisher The publisher is already there on the item when the broadcaster gets it, so it needs to do the opposite thing.
Sun, 25 Jul 2021 14:01:45 +0200 mod_pubsub: Normalize 'publisher' JID
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 14:01:45 +0200] rev 11721
mod_pubsub: Normalize 'publisher' JID All the XEP-0060 examples have the publisher attribute set to a bare JID, but the text does allow it to be the full JID. Since mod_pubsub is more likely used for open nodes that anyone can subscribe to it makes sense to not leak the full JIDs. This is also disabled by defaults. In mod_pep on the other hand it might make sense to have the full JID since that data is more likely to be broadcast to contacts which are already somewhat trusted.
Sun, 25 Jul 2021 13:52:52 +0200 scansion tests: Enable 'expose_publisher' since we test for it
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 13:52:52 +0200] rev 11720
scansion tests: Enable 'expose_publisher' since we test for it
Sun, 25 Jul 2021 13:52:27 +0200 mod_pubsub: Respect 'expose publisher' setting in item retrieval
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 13:52:27 +0200] rev 11719
mod_pubsub: Respect 'expose publisher' setting in item retrieval
Wed, 01 May 2019 22:33:22 +0200 mod_pubsub: Fix inclusion of publisher (fixes #1399)
Kim Alvefur <zash@zash.se> [Wed, 01 May 2019 22:33:22 +0200] rev 11718
mod_pubsub: Fix inclusion of publisher (fixes #1399)
Fri, 23 Jul 2021 17:13:06 +0200 Merge 0.11->trunk
Kim Alvefur <zash@zash.se> [Fri, 23 Jul 2021 17:13:06 +0200] rev 11717
Merge 0.11->trunk
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip