Mercurial > prosody-modules
view mod_muc_ban_ip/README.markdown @ 4942:e7b9bc629ecc
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.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 16 May 2022 19:47:09 +0200 |
parents | 8de50be756e5 |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Ban users from chatrooms by their IP address ... Introduction ============ One frequent complaint about XMPP chatrooms (MUCs) compared to IRC is the inability for a room admin to ban a user based on their IP address. This is because an XMPP user is not identified on the network by their IP address, only their JID. This means that it is possible to create a new account (usually quite easily), and rejoin the room that you were banned from. This module allows the **user's** server to enforce bans by IP address, which is very desirable for server admins who want to prevent their server being used for spamming and abusive behaviour. Details ======= An important point to note is that this module enforces the IP ban on the banned user's server, not on the MUC server. This means that: - The user's server MUST have this module loaded, however - - The module works even when the MUC is on a different server to the user - The MUC server does not need this module (it only needs to support the [standard ban protocol](http://xmpp.org/extensions/xep-0045.html#ban)) - The module works for effectively banning [anonymous users](http://prosody.im/doc/anonymous_logins) Also note that IP bans are not saved permanently, and are reset upon a server restart. Configuration ============= There is no extra configuration for this module except for loading it. Remember... do not load it on the MUC host, simply add it to your global `modules_enabled` list, or under a specific host like: ``` lua VirtualHost "anon.example.com" authentication = "anonymous" modules_enabled = { "muc_ban_ip" } ``` Compatibility ============= ----- -------------- 0.9 Works 0.8 Doesn't work ----- --------------