Implement support for MSC4140: Cancellable delayed events #903
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#903
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://github.com/matrix-org/matrix-spec-proposals/pull/4140
This MSC allows clients to schedule events by offloading the wait to the server. It also allows that event to be cancelled in future.
This feature is used by Element Call in order to reliably un-stuck calls in the event a client disconnects before it can send the leave call payload. It could also have interesting implications for reminder bots and such.
https://github.com/matrix-construct/tuwunel/issues/105 Same problem as tuwunel,Notifications on Element X are often delayed and sporadic
@utop-top wrote in #903 (comment):
Element X receiving delayed notifications is a separate issue, this is a feature proposal to improve things like Element Call. If you're having issues with Element X, feel free to open a different issue with some more info
@utop-top that's unrelated to this feature.
@nex wrote in #903 (comment):
My attempt to create a new ticket failed