Skip to content
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.

Sign up for GitHub

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

Jump to bottom

API to report ability to deliver messages to a given user. #482

Open
ara4n opened this issue Jun 6, 2019 · 0 comments
Open

API to report ability to deliver messages to a given user. #482

ara4n opened this issue Jun 6, 2019 · 0 comments
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@ara4n
Copy link
Member

ara4n commented Jun 6, 2019

If our local server is unable to currently send messages to a remote server (or indeed an AS or a remote bridge, or even a local user in a sharded world) there should be some mechanism to report presence data back to your client to tell you that messages to that user aren't getting through. Extra points if we can guesstimate how delayed the queue is.
@turt2live turt2live added A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol labels Jun 6, 2019
@ericmigi ericmigi mentioned this issue Jun 23, 2019
Open
@V02460 V02460 mentioned this issue Jul 10, 2019
Open
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@richvdh richvdh mentioned this issue Mar 1, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@turt2live @ara4n