mod_http_muc_log: Drop support for pre-0.11 MUC API The oldest supported Prosody branch is 0.11, therefore we can drop code for the MUC API of Prosody 0.10 and before. The module:shared("rooms") method was never even in a release...

mod_csi_battery_saver: Add support for urn:xmpp:jingle-message:1 (XEP-0353)

mod_cloud_notify: Compat for prosody 0.12

mod_firewall: README: Fix grammar and further improve wording

mod_firewall: README: Clarify when storage access can occur with roster checks

mod_firewall: README: Correct mention of 'JUMP_CHAIN' to 'JUMP CHAIN'

mod_ping_muc/README: Update Compatibility section for 0.12 going stable

mod_http_muc_log: Show XEP-0444 reactions

mod_muc_restrict_media: Don't apply restriction to affiliated users Looks like an oversight. Assuming that all truthy affiliations are valid, and that "outcast" would not reach this point anyway.

mod_pubsub_post/README: Update references to trunk with release numbers

mod_muc_ping: Remove since Prosody mod_muc 0.11+ covers this natively See trunk rev 7c1cdf5f9f83 and trunk rev 224e681c4db2

mod_rest: Add various things to openapi spec These are already in xmpp-schema.json

mod_rest: Add some descriptive details to schema

mod_profile: Obsolete. Remove. Redirect to mod_vcard_legacy

mod_http_admin_api: Update for 0.12 changes to mod_smacks

mod_rest: Provide a log function on temporary session Fixes traceback in places using session.log()

merge upstream

mod_delegation: use clean_xmlns to remove jabber:client namespace from node: for the same reason as in mod_privilege, `jabber:client` namespace is removed with the clean_xmlns method coming from there. Furthermore, the forwarded <iq> stanza use the `jabber:client` xmlns while the stanza may come from a component with e.g. `jabber:component:accept` xmlns, this can lead to inconsistencies between the <iq> stanza and children (like <error> element).

mod_rest: Add an example OAuth client (needs mod_http_oauth2)

mod_muc_occupant_id: Update Compatibility to mention being built-in in 0.12

mod_muc_auto_reserve_nicks: Force refresh of nickname (thanks phryk)

mod_rest: Add mapping of XEP-0380: Explicit Message Encryption Useful since OMEMO etc isn't mapped

mod_rest: Document /archive/ in openapi spec

mod_rest: Treat archive.ids as comma-separated to work in query string Can't easily put an array into a query string. Hope nobody puts commas into their archive ids.

mod_reload_modules: Be aware of component module (thanks Menel) Without this, the component module is seen as a module that is loaded but not configured, and is thus unloaded

mod_onions: Fix for bitop with Lua 5.4

mod_net_proxy: Fix for bitop with Lua 5.4

mod_rest: Fix attempt to index nil in handling of single iq response Fix handling of many responses, break handling of single response :(

mod_rest: Ensure MAM result-iq is included in results from remote hosts Needed for the same reason as the special message handling, the remote route does not pass our origin.send() here

mod_rest: Add special handling to catch MAM results from remote hosts Makes MAM queries to remote hosts works. As the comment says, MAM results from users' local archives or local MUCs are returned via origin.send() which is provided in the event and thus already worked. Results from remote hosts go via normal stanza routing and events, which need this extra handling to catch. This pattern of iq-set, message+, iq-result is generally limited to MAM. Closest similar thing might be MUC join, but to really handle that you would need the webhook callback mechanism.