Spam-resistant invites #34
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have learned the hard way that the way Matrix handles invites is in no way resistant to spam. While this is largely an issue with moderation that should be solved by, well, proper moderation, it may also be helpful to consider ways to reduce the impact, both preemptively (so that invite spam becomes less viable) and after the fact (easily resetting the invites for all affected users, with options to use from the source's end, a server or community moderator's end, and also for the users who get the spam).
We were reading about how WhatsApp does or will do username invites today and you have to input a pin that is shared with you by the user you wish to add. We think perhaps this is a good method for this perhaps in some use cases.
Perhaps this could be a user enabled option or some such.