Moderator/user looses participant type and custom permissions when leaving and rejoining
Open
Nobody has claimed this yet.
bug
feature: conversations 👥
papercut
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Be moderator in a "Office chat"
- Be in a focus period with upcoming vacation and try to focus
- Leave the conversation to be less distracted
- After vacation join the open conversation again
Expected behaviour
✨
Actual behaviour
You got demoted, custom permissions are removed (could also end in more permissions then before, so a user could "evade a chat ban")
Talk app
**Talk app version:**main
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 reproducing the listed leave-and-rejoin steps in a Talk conversation and trace how participant type and custom permissions are restored. Done means a moderator retains the correct participant type and permissions after rejoining, without gaining permissions that could evade a chat ban; no source file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100