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

surely /context should return state as of first event, for consistency with /sync (SPEC-424) #187

Open
matrixbot opened this issue Jul 6, 2016 · 2 comments
Open

surely /context should return state as of first event, for consistency with /sync (SPEC-424) #187

matrixbot opened this issue Jul 6, 2016 · 2 comments
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol p4 wart A point where the protocol is inconsistent or inelegant

Comments

@matrixbot
Copy link
Member

Submitted by @​matthew:matrix.org

(Imported from https://matrix.org/jira/browse/SPEC-424)
@matrixbot
Copy link
Member Author

Jira watchers: @richvdh

@matrixbot
Copy link
Member Author

I agree, but fixing it is likely to be a PITA at this point.

-- @richvdh

@matrixbot matrixbot added the p4 label Oct 28, 2016
@matrixbot matrixbot mentioned this issue Oct 28, 2016
Closed
@matrixbot matrixbot changed the title surely /context should return state as of first event, for consistency with /sync surely /context should return state as of first event, for consistency with /sync (SPEC-424) Oct 31, 2016
@matrixbot matrixbot added spec-bug Something which is in the spec, but is wrong cs-v3 labels Nov 7, 2016
@richvdh richvdh added enhancement A suggestion for a relatively simple improvement to the protocol and removed spec-bug Something which is in the spec, but is wrong labels Nov 21, 2016
@richvdh richvdh mentioned this issue Jul 27, 2018
Merged
@turt2live turt2live added wart A point where the protocol is inconsistent or inelegant A-Client-Server Issues affecting the CS API labels Feb 6, 2019
@MadLittleMods MadLittleMods mentioned this issue Oct 13, 2021
Closed
27 tasks
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@richvdh richvdh removed the cs-v3 label Mar 2, 2022
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 p4 wart A point where the protocol is inconsistent or inelegant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@turt2live @richvdh @matrixbot