matrix-org / matrix-org/matrix-spec

Push: Flag events from the events stream that must be notified to the end user (SYN-304)

Open
#874 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-Push enhancement
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

Currently, every client platform must implement the push rules logic in order to manage in-app notifications.
So, there is N implementations of them which seems risky in term of bug.

Could we keep the logic in one place: the homeserver and make the homeserver notify clients with additional information in events coming down the events stream?

(Imported from https://matrix.org/jira/browse/SYN-304)

(Reported by @manuroe)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the issue's proposal to move push-rule logic from client platforms into the homeserver and expose notification information in the events stream. The work needs a concrete specification scope and agreement on the event data and behavior; done would be an agreed, implementable protocol change.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.