matrix-org / matrix-org/matrix-bifrost
Handle conflicting nicknames
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 you try to join to XMPP MUC and there will be a user with that same nickname as your Matrix account nickname you will join as usual but no virtual user appear on XMPP side and none of your messages will be delivered to the MUC without you knowing that (see also #203).
**Describe the solution you'd like**
Maybe rename the user adding some suffix to the nickname.
**Describe alternatives you've considered**
Maybe give user read-only permission by default and create PM with the user asking him to set another `/roomnick` in that room so he can speak after that.
**Additional context**
None.
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 reviewing the XMPP MUC nickname-handling behavior described here and the related issue #203, including the `/roomnick` flow. Done means a conflicting nickname is handled explicitly, the virtual user can participate or the user is clearly informed of the required action, and messages are not silently lost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100