view mod_invites_tracking/README.md @ 5173:460f78654864

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.
author Jonas Schäfer <jonas@wielicki.name>
date Tue, 21 Feb 2023 21:37:27 +0100
parents 32f1f18f4874
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: 'Store who created the invite to create a user account'
...

Introduction
============

Invites are an intermediate way between opening registrations completely and
closing registrations completely.

By letting users invite other users to the server, an administrator exposes
themselves again to the risk of abuse.

To combat that abuse more effectively, this module allows to store (outside
of the user’s information) who created an invite which was used to create the
user’s account.

Details
=======

Add to `modules_enabled`.

Caveats
=======

- The information is not deleted even when the associated user accounts are
  deleted.
- Currently, there is no way to make any use of that information.