mod_register_apps: Detect 0.12+ when called from prosodyctl Otherwise it loads mod_http_files which logs a warning

mod_muc_rtbl: fix more incorrect more references to "event"

mod_muc_rtbl: ignore blocklist for affiliated users for messages Just like we ignore the blocklist for join attempts from affiliated users, we also do that now on messages.

mod_muc_rtbl: fix traceback because of scoping error There is no "event" there, we have to use the occupant data instead. That's what you get for moving code around!

mod_muc_rtbl: move use of "private" attributes to single function This way, we reduce the scope where you can have a typo in the attribute name to that function and we encourage users to actually always call update_hashes.

mod_muc_rtbl: also filter messages This was a bit tricky because we don't want to run the JIDs through SHA256 on each message. Took a while to come up with this simple plan of just caching the SHA256 of the JIDs on the occupants. This will leave some dirt in the occupants after unloading the module, but that should be ok; once they cycle the room, the hashes will be gone. This is direly needed, otherwise, there is a tight race between the moderation activities and the actors joining the room.

New module, mod_muc_reserve_nick_pattern

Strip images from XHTML-IM as well

mod_muc_moderation: Derive role from reserved nickname if occupant When using a different client to moderate than the one used to participate in the chat, e.g. a command line tool like clix, there's no occupant and no role to use in the permission check. Previously the default role based on affiliation was used. Now if you are present in the room using your reserved nick, the role you have there is used in the permission check instead of the default affiliation-derived role.

mod_muc_moderation: Refactor to prepare for new version of XEP-0425 Plan is to add support for both versions concurrently for a transition period while clients upgrade.