Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | mod_pep: Set correct jid attr on node disco items | Kim Alvefur | 2021-12-07 | 1 | -0/+1 |
| | | | | | It was previously set to the hostname, not the users bare JID which would be correct. | ||||
* | mod_pubsub,mod_pep: Advertise maximum number of items via XEP-0122 | Kim Alvefur | 2021-10-20 | 1 | -0/+7 |
| | | | | | | Clients would generally be using the "max" symbol instead of discovering this, but this also gets us validation and earlier rejection of out of bounds values. | ||||
* | mod_pubsub,mod_pep: Implement 'send_last_published_item' option #1436 | Kim Alvefur | 2021-10-19 | 1 | -0/+3 |
| | | | | | | | | Default left as 'never' in mod_pubsub to preserve the previous behavior. Unclear if this is desirable, but can always be changed later. In mod_pep this allows turning off the automatic resending of most recent item. | ||||
* | mod_pep: Remove now unused util.cache import | Kim Alvefur | 2021-07-25 | 1 | -1/+0 |
| | |||||
* | mod_pep: Remove use of RLU cache when persist_items was set to false | Kim Alvefur | 2021-07-21 | 1 | -8/+3 |
| | | | | | | | | 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. | ||||
* | mod_pubsub,mod_pep: Support "max" as 'pubsub#max_items' | Kim Alvefur | 2021-06-09 | 1 | -3/+11 |
| | | | | | | Fixes #1643 API change: The argument to archive_itemstore() changes type to integer | ||||
* | Merge 0.11->trunk | Kim Alvefur | 2021-05-16 | 1 | -12/+0 |
|\ | |||||
| * | mod_pep: Remove obsolete node restoration code (now done by util.pubsub) | Kim Alvefur | 2021-05-16 | 1 | -12/+0 |
| | | | | | | | | | | | | | | | | | | | | | | | | Originally added in 202b9951b037 but util.pubsub gained a better method in 6c2c2fc4b8dd since then, which mod_pep uses since 9194431b6447 which should have deleted this. All these :create calls would have failed with a 'conflict' error, since the nodes had already been created. This was never noticed because of missing error handling. Also note that this code did not restore node configuration. | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2021-02-15 | 1 | -0/+1 |
|\| | |||||
| * | mod_pep: Advertise base pubsub feature (fixes #1632)0.11.8 | Kim Alvefur | 2021-02-15 | 1 | -0/+1 |
| | | | | | | | | | | Noticed while discussing feature discovery in Gajim Thanks lovetox | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2020-02-27 | 1 | -1/+1 |
|\| | |||||
| * | mod_pubsub, mod_pep: Ensure correct number of children of <item/> (fixes #1496) | Kim Alvefur | 2020-02-27 | 1 | -1/+1 |
| | | |||||
* | | Merge 0.11->trunk | Kim Alvefur | 2019-12-23 | 1 | -34/+17 |
|\| | |||||
| * | mod_pep: Handle presence subscriptions in filter (fixes #1372) | Kim Alvefur | 2019-06-10 | 1 | -34/+17 |
| | | | | | | | | Take two on 045209b41b3a | ||||
* | | mod_pep: Only log when creating new pubsub services | Kim Alvefur | 2019-07-09 | 1 | -1/+1 |
| | | | | | | | | | | | | | | Once upon a time get_pep_service() would get called with random bare JIDs and remote hostnames, which is why it was logged this way. This seems to have been fixed, so it's not as useful anymore. It's still useful to know when it creates a new service object. | ||||
* | | mod_pep: Log node name instead of payload | Kim Alvefur | 2019-06-16 | 1 | -1/+1 |
| | | | | | | | | Having the node logged is more useful and less problematic for privacy | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2019-06-10 | 1 | -5/+10 |
|\ \ | |/ |/| | |||||
| * | Merge 0.11->trunk | Kim Alvefur | 2019-05-30 | 1 | -39/+16 |
| |\ | |||||
| * \ | Merge 0.11->trunk | Kim Alvefur | 2019-02-22 | 1 | -1/+3 |
| |\ \ | |||||
| * | | | mod_pep: Set an 'id' on notifications | Kim Alvefur | 2018-12-23 | 1 | -1/+3 |
| | | | | | | | | | | | | | | | | mod_pubsub got this in f2d35eee69c9 | ||||
| * | | | mod_pep: Add some spacing between blocks in broadcaster to improve readability | Kim Alvefur | 2018-12-23 | 1 | -0/+3 |
| | | | | |||||
| * | | | mod_pep: Move broadcaster code around to be more like in mod_pubsub | Kim Alvefur | 2018-12-23 | 1 | -3/+6 |
| | | | | | | | | | | | | | | | | This eases comparing and contrasting these two modules. | ||||
| * | | | mod_pep: Remove incorrect features advertised on the bare host | Kim Alvefur | 2018-11-01 | 1 | -3/+0 |
| | | | | |||||
* | | | | mod_pep: Revert 045209b41b3a, caused a regression | Kim Alvefur | 2019-06-10 | 1 | -17/+37 |
| |_|/ |/| | | | | | | | | | | | | | | Adding in all presence based subscriptions in the broadcaster caused resend_last_item() to unintentionally send out more notifications than it should have. | ||||
* | | | mod_pep: Handle presence based subscription outside of util.pubsub (fixes #1372) | Kim Alvefur | 2019-05-30 | 1 | -37/+17 |
| |/ |/| | | | | | | | | | | | | | | | Subscriptions were updated for each incoming presence stanza from contacts. Each subscription change triggered a configuration save, which would filter out the presence based subscriptions and usually end up replacing the existing data with identical data. With many subscribed nodes this adds up to a fair bit of IO bound work that is avoided by keeping them separate. | ||||
* | | mod_pep: Simplify configuration for node data (fixes #1320) | Kim Alvefur | 2019-02-22 | 1 | -1/+3 |
|/ | |||||
* | pubsub: Set pubsub#title as name attribute in disco#items (fixes #1226) | Kim Alvefur | 2018-10-30 | 1 | -1/+1 |
| | |||||
* | mod_pep: Add automatic subscriptions on node creation (fixes #1222) | Kim Alvefur | 2018-10-20 | 1 | -1/+21 |
| | | | | | Replaces automatic node creation on subscription, since this casues problems when trying to keep nodes private or other specific settings. | ||||
* | mod_pep: Add PEP service owners username in configuration to ease identification | Kim Alvefur | 2018-10-20 | 1 | -0/+1 |
| | |||||
* | mod_pep: Remove use of recipients table for signaling pending disco#items | Kim Alvefur | 2018-10-23 | 1 | -16/+7 |
| | | | | | | | | | | It stored the caps hash as a string in the recipients table while waiting for a disco#info response, then replaces it with the set of nodes that had +notify. This mixing of types is bad, so here it gets removed. This can be improved once an IQ tracking API (#714) is added. | ||||
* | mod_pep: Add all pubsub service objects to item API in order to behave ↵ | Kim Alvefur | 2018-10-20 | 1 | -0/+4 |
| | | | | across reloads | ||||
* | mod_pep: Simplify code | Matthew Wild | 2018-08-18 | 1 | -2/+1 |
| | |||||
* | mod_pep: Remove feature for persistence already added elsewere | Kim Alvefur | 2018-08-18 | 1 | -1/+0 |
| | | | | This is added in pubsub.lib | ||||
* | mod_pep: Remove already included access model feature | Kim Alvefur | 2018-08-18 | 1 | -1/+0 |
| | | | | access-* is added in pubsub.lib based on node defaults | ||||
* | mod_pep: Respect setting for whether to include payload in notifications | Kim Alvefur | 2018-08-16 | 1 | -0/+5 |
| | |||||
* | mod_pep: Respect settings for which kinds of notifications to send | Kim Alvefur | 2018-08-16 | 1 | -1/+6 |
| | |||||
* | util.pubsub: Pass "retract" as the type of such broadcasts | Kim Alvefur | 2018-08-16 | 1 | -0/+3 |
| | | | | | | | | This moves some XEP-0060 awkwardness out of util.pubsub and into mod_pubsub A retraction is broadcast in an <items> container, whereas most other kinds of broadcasts are in a container with a name matching the 'kind' attribute. | ||||
* | mod_pep, util.pubsub: Rename restricted->outcast, none->member and add new ↵ | Matthew Wild | 2018-08-08 | 1 | -5/+2 |
| | | | | 'none' affiliation to better match XEP-0060 | ||||
* | mod_pubsub, mod_pep, util.pubsub: Move capability definitions into ↵ | Matthew Wild | 2018-08-08 | 1 | -78/+0 |
| | | | | util.pubsub to avoid duplication | ||||
* | mod_pep: Add comment explaining 'none' affiliation | Matthew Wild | 2018-08-08 | 1 | -0/+3 |
| | |||||
* | mod_pep: Remove "subscriber" affiliation in favour of "none" | Matthew Wild | 2018-08-08 | 1 | -23/+1 |
| | | | | | It ended up with identical capabilities to "none", and isn't a standard affiliation defined by XEP-0060 anyway. | ||||
* | mod_pep: Loosen restrictions on the "none" affiliation | Kim Alvefur | 2018-08-08 | 1 | -6/+6 |
| | | | | | | | This allows non-contacts access to data in nodes with the "open" access model. Thanks gerald | ||||
* | mod_pep: Change default affiliation in the "presence" access model to ↵ | Kim Alvefur | 2018-08-08 | 1 | -0/+1 |
| | | | | | | | "restricted" for non-contacts This lets us loosen the restrictions of the "none" affiliation, so that the "open" access model allows anyone basic access. | ||||
* | mod_pep: Add comment about 'hash_map' table | Kim Alvefur | 2018-08-06 | 1 | -0/+2 |
| | |||||
* | mod_pep: Correct comment about 'recipients' table | Kim Alvefur | 2018-08-06 | 1 | -1/+1 |
| | |||||
* | mod_pep: Pass 'recipients' table across module reloads | Kim Alvefur | 2018-08-06 | 1 | -1/+5 |
| | |||||
* | mod_pep: Only resend last item on successful subscription | Kim Alvefur | 2018-08-05 | 1 | -2/+3 |
| | |||||
* | mod_pubsub, mod_pep: The "restricted" affiliation should be allowed to be ↵ | Kim Alvefur | 2018-08-06 | 1 | -0/+4 |
| | | | | | | unsubscribed but nothing else Can't revoke their subscriptions on change of access model otherwise | ||||
* | mod_pep: Save non-presence based subscriptions to storage | Kim Alvefur | 2018-08-05 | 1 | -2/+7 |
| | |||||
* | mod_pep: Note which subscriptions are presence based as subscription option | Kim Alvefur | 2018-08-05 | 1 | -1/+1 |
| |