146
edits
(Add Category) |
|||
Line 26: | Line 26: | ||
(this mechanism doesn't cover MUCs which don't reflect the message ID and do autopastebin. Screw them!) | (this mechanism doesn't cover MUCs which don't reflect the message ID and do autopastebin. Screw them!) | ||
= Mediated MUC Invitations = | |||
The default mechanism to invite somebody into a MUC is [https://xmpp.org/extensions/xep-0045.html#invite-mediated §7.8.2 Mediated Invitation], where the MUC service will invite your friend on your behalf. | |||
* Some MUC services will not invite a JID that is already a MUC member, thus breaking the invitation UX. | |||
* With Mediated Invites, a malicious MUC can send an invite in the name of a user's contact, tricking the user's client into auto-joining. | |||
* [https://xmpp.org/extensions/xep-0249.html XEP-0249: Direct MUC Invitations] is a potential solution to those issues. | |||
= Am I still there? = | = Am I still there? = | ||
Line 34: | Line 43: | ||
Sending a "silent" message or presence update to the MUC will lead to O(N²) complexity (if every client does so), killing all our batteries. | Sending a "silent" message or presence update to the MUC will lead to O(N²) complexity (if every client does so), killing all our batteries. | ||
This is solved by [https://xmpp.org/extensions/xep-0410.html XEP-0410: MUC Self-Ping] | |||
= MUC double join = | = MUC double join = |