Software /
code /
prosody-modules
File
mod_block_registrations/mod_block_registrations.lua @ 4515:2e33eeafe962
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked
Original intention was to leave alone things that this module isn't
handling. However markers in archives are just problematic without
more advanced logic about what is markable and what is not. It also
requires a more advanced query in mod_muc_rai to determine the latest
markable message instead of the latest archived message.
I'd rather keep the "is archivable" and "is markable" definition the
same for simplicity. I don't want to introduce yet another set of rules
for no reason.
No markers in MAM.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Mon, 22 Mar 2021 15:55:02 +0000 |
parent | 1697:27aa58ed3e2e |
child | 5065:368bf9b06484 |
line wrap: on
line source
local st = require "util.stanza"; local nodeprep = require "util.encodings".stringprep.nodeprep; local block_users = module:get_option_set("block_registrations_users", { "admin" }); local block_patterns = module:get_option_set("block_registrations_matching", {}); local require_pattern = module:get_option_string("block_registrations_require"); function is_blocked(username) -- Check if the username is simply blocked if block_users:contains(username) then return true; end for pattern in block_patterns do if username:find(pattern) then return true; end end -- Not blocked, but check that username matches allowed pattern if require_pattern and not username:match(require_pattern) then return true; end end module:hook("user-registering", function(event) local username = event.username; if is_blocked(username) then event.allowed = false; return true; end end, 10);