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

We need to figure out how to linearize history for client consumption. (SPEC-65) #474

Closed
matrixbot opened this issue Nov 6, 2014 · 5 comments
Closed

We need to figure out how to linearize history for client consumption. (SPEC-65) #474

matrixbot opened this issue Nov 6, 2014 · 5 comments
Labels
client-server Client-Server API feature Suggestion for a significant extension which needs considerable consideration p2

Comments

@matrixbot
Copy link
Member

We currently use a very, very naive algorithm for converting the event graph into linear history. The major problem is correctly handling conflicting state updates.

(Imported from https://matrix.org/jira/browse/SPEC-65)

(Reported by @erikjohnston)
@matrixbot
Copy link
Member Author

Jira watchers: @erikjohnston

@matrixbot matrixbot added the p2 label Oct 28, 2016
@matrixbot matrixbot changed the title We need to figure out how to linearize history for client consumption. We need to figure out how to linearize history for client consumption. (SPEC-65) Oct 31, 2016
@matrixbot matrixbot added the feature Suggestion for a significant extension which needs considerable consideration label Nov 7, 2016
@turt2live turt2live added the client-server Client-Server API label Feb 6, 2019
@ara4n
Copy link
Member

ara4n commented Aug 4, 2020

Is this is the spec version of matrix-org/matrix-spec#1209?

@richvdh
Copy link
Member

richvdh commented Aug 4, 2020

I think it's related, but different. My reading of the summary of this issue is that we don't have a good way of handling events that turn up very late. (Currently we just spit them out over /sync regardless, but then put them in a different place when paginating with /messages, which confuses users and clients alike.)

@richvdh
Copy link
Member

richvdh commented Aug 4, 2020

(I'm not sure that matrix-org/matrix-spec#1209 has a spec version)

@richvdh richvdh mentioned this issue Sep 20, 2021
Open
@richvdh
Copy link
Member

richvdh commented Sep 20, 2021

I'm going to close this, because we did, to some extent, figure out how to linearize history. It's unclear that it's a good solution (see #2849, matrix-org/matrix-spec#852, matrix-org/matrix-spec#859), but those are kinda separate problems.

@richvdh richvdh closed this as completed Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
client-server Client-Server API feature Suggestion for a significant extension which needs considerable consideration p2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@turt2live @ara4n @richvdh @matrixbot