matrix-org / matrix-org/matrix-bifrost
Kick the user from Matrix room if virtual user can’t join XMPP chat
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 187
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
If a user can’t join XMPP chat (see #202 for instance) then in the Matrix chat the user will have no sings of it, their messages just won’t be delivered without knowing that by anyone in Matrix chat. XMPP users also may be confused by loosing some context whilst people can chat with an invisible user.
**Describe the solution you'd like**
Kick a user if their XMPP avatar has failed to join the MUC.
**Describe alternatives you've considered**
Instead of kicking the user you can give him read-only access for instance.
**Additional context**
See also #203 as another example of when a virtual user fails to join XMPP MUC.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #202 and the bridge's XMPP MUC join and Matrix virtual-user handling entry points. Trace the failure path when an XMPP avatar cannot join the MUC, then verify that the Matrix user is removed or restricted and that successful joins remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100