matrix-org / matrix-org/matrix-spec
Users registered by an appservice should not have server-default notifications enabled.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
By default, users are [given some server-default notification](https://spec.matrix.org/v1.4/client-server-api/#predefined-rules) which the server will then spend some of it's time calculating for that user. Appservice users are no different, so your average IRC ghost user will *also* have notifications counted for them.
In all but the 0.01% of cases, appservice users generally don't need to receive notifications at all, so we could save everyone some computational cost by disabling server-default notification rules by default if the user was registered with a `type` of `m.login.application_service`.
We could probably add a flag to enable them anyway, if so desired.
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 with the linked Matrix Client-Server API section on predefined rules and the registration behavior for users whose type is m.login.application_service. Done means the specification clearly defines whether server-default notification rules are disabled for these users and how any opt-in flag should work.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100