Software /
code /
prosody-modules
File
mod_track_muc_joins/README.md @ 6112:4c0e3fe57e92
mod_compliance_latest: Gracefull error logging on missing dependency.
diff --git a/mod_compliance_latest/README.md b/mod_compliance_latest/README.md
--- a/mod_compliance_latest/README.md
+++ b/mod_compliance_latest/README.md
@@ -9,13 +9,15 @@ rockspec:
# Introduction
-This module will always require and load to the lastest compliance tester we have in the community modules.
-Currently this is [mod_compliance_2023].
+This meta-module will always `require` (and therefore auto-load) the lastest compliance tester we have in the community modules.
+Currently this is [mod_compliance_2023]. See the linked module for further details.
+
+If you do not use the *Prosody plugin installer* this module will likely have limited value to you.
+You can also just install the current compliance tester manually.
# Configuration
-Just load this module as any other module and it will automatically install [mod_compliance_2023] if you use the Prosody plugin installer.
-See the linked module for further details.
+Just load this module as any other module and it will automatically install and load [mod_compliance_2023] if you use the *Prosody plugin installer*.
# Compatibility
diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua
--- a/mod_compliance_latest/mod_compliance_latest.lua
+++ b/mod_compliance_latest/mod_compliance_latest.lua
@@ -1,1 +1,6 @@
-module:depends("compliance_2023");
+local success, err = pcall(function() module:depends("compliance_2023") end)
+
+if not success then
+ module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?")
+ return 1, "Error: Couldn't load dependency mod_compliance_2023."
+end
author | Menel <menel@snikket.de> |
---|---|
date | Mon, 23 Dec 2024 12:58:03 +0100 |
parent | 6003:fe081789f7b5 |
line wrap: on
line source
--- summary: Keep track of joined chat rooms ... # Introduction This module attempts to keep track of what MUC chat rooms users have joined. It's not very useful on its own, but can be used by other modules to influence decisions. # Usage Rooms joined and the associated nickname is kept in a table field `rooms_joined` on the users session. An example: ``` lua local jid_bare = require"util.jid".bare; module:hook("message/full", function (event) local stanza = event.stanza; local session = prosody.full_sessions[stanza.attr.to]; if not session then return -- No such session end local joined_rooms = session.joined_rooms; if not joined_rooms then return -- This session hasn't joined any rooms at all end -- joined_rooms is a map of room JID -> room nickname local nickname = joined_rooms[jid_bare(stanza.attr.from)]; if nickname then session.log("info", "Got a MUC message from %s", stanza.attr.from); local body = stanza:get_child_text("body"); if body and body:find(nickname, 1, true) then session.log("info", "The message contains my nickname!"); end end end); ``` # Known issues [XEP 45 § 7.2.3 Presence Broadcast][enter-pres] has the following text: > In particular, if roomnicks are locked down then the service MUST do > one of the following. > > \[...\] > > If the user has connected using a MUC client (...), then the service > MUST allow the client to enter the room, modify the nick in accordance > with the lockdown policy, and **include a status code of "210"** in > the presence broadcast that it sends to the new occupant. This case is not yet handled. [enter-pres]: http://xmpp.org/extensions/xep-0045.html#enter-pres