[WIP] MSC3361: Opportunistic Direct Push #3361
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukaslihotzki
changed the title
lukaslihotzki
changed the title
lukaslihotzki
force-pushed
the
opportunistic-direct-push
branch
from
b15a848
to
f218b4f
Compare
turt2live
added
kind:feature
lukaslihotzki
force-pushed
the
opportunistic-direct-push
branch
from
f218b4f
to
f717e0f
Compare
turt2live
reviewed
Mar 3, 2023
|
|
||
| ## Proposal | ||
|
|
||
| A new property is added to the response scheme of the `sync` operation: The `notifications` property with type `[Notification]` (like in `getNotifications`). The homeserver can use this property to deliver notifications directly. |
There was a problem hiding this comment.
apologies for the extraordinarily late review, but could the device also just run the push rules locally on messages it receives?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered