matrix-org / matrix-org/matrix-bifrost
Room/MUC should have the same Room rights as the bridged Room
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 187
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When i have a Matrix room where only Moderators/Admins can write, XMPP-Usern shouldn't be able to write as well.
To Reproduce
- Create a Matrix Room where only Moderators/Admins can write
- join it with a XMPP Account.
- you can write messages which won't be bridged to the Matrix-Room but can be seen by other XMPP-Users.
Expected behavior
The XMPP/Matrix rights should be nearly* the same
(* as far as possible. e.G. when a XMPP User joins a Matrix Room where only Moderators and Admins are allowed to join, then a moderated MUC should be created.)
Additional context
Perhaps a quick and dirty solution for Moderated Rooms/MUC could be allowing to write, but if the other bridged MUC/Room "reject" the message, it get deleted in the Gateway-Room/MUC aswell.
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
Reproduce the issue using the Matrix room and XMPP account steps, then trace the bridge's handling of room permissions and MUC message delivery. Done means XMPP users cannot post where the bridged Matrix room rejects them, with the reported moderated-room behavior handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100