Skip to content

[WIP] MSC3359: Delayed Push #3359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: old_master
Choose a base branch
from

Conversation

jcgruenhage
Copy link
Contributor

@jcgruenhage jcgruenhage commented Aug 25, 2021

Rendered

This is a placeholder to reserve the number, a proposal will follow shortly. For the curious, a short description is already included.

@jcgruenhage jcgruenhage force-pushed the jcgruenhage/delayed-push branch from a0307da to e54147f Compare August 25, 2021 09:19
@jcgruenhage jcgruenhage changed the title MSC3359: Delayed Push WIP: MSC3359: Delayed Push Aug 25, 2021
@jcgruenhage jcgruenhage changed the title WIP: MSC3359: Delayed Push [WIP] MSC3359: Delayed Push Aug 25, 2021
@uhoreg uhoreg added client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff proposal A matrix spec change proposal push labels Aug 25, 2021
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Sep 28, 2021
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI matrix-org/synapse#15516 was implemented, which allows an administrator of Synapse to determine a homeserver-wide random jitter for push notifications. That differs from this proposal, which allows clients to specify the amount of jitter they want.

Given this, do you think that client-side jitter specification is still important? Or is implementing it in the homeserver enough for your needs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal push
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants