matrix-org / matrix-org/matrix-spec
what is the actual point of per-room pushrules?
Open
Nobody has claimed this yet.
A-Client-Server
A-Push
wart
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
since you can only have one per-room pushrule, if you want to do anything more intelligent than 'treat all events in this room the same', you end up using overrides or underrides anyway
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
Read the push-rule section of the Matrix specification and review the existing eight-comment discussion. Done means the purpose and limitations of per-room push rules are clarified, with an agreed direction for whether the specification should change.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100