matrix-org / matrix-org/matrix-hookshot
Clean up ghost users after being removed from a room
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 450
- Forks
- 95
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 23
Description
**Is your feature request related to a problem? Please describe.**
When the Hookshot user has been removed from the room, any ghost users will be left behind.
**Describe the solution you'd like**
When the main Hookshot bot has been removed/kicked from a room, any ghost users it has invited (e.g. from webhooks) should leave the room too.
**Describe alternatives you've considered**
Otherwise, user needs to manually remove each ghost user.
**Additional context**
This may also include cleaning up connections?
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
No file, test, or entry point is named in the issue. Start by locating the handling for the Hookshot bot being removed from a room and the lifecycle of invited ghost users; done means those users also leave, with any connection cleanup clarified and covered by tests.
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