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

rapid fire message order #1

Open
kfatehi opened this issue Dec 11, 2016 · 2 comments
Open

rapid fire message order #1

kfatehi opened this issue Dec 11, 2016 · 2 comments

Comments

@kfatehi
Copy link
Member

kfatehi commented Dec 11, 2016

all messages arrive, but the order is not guaranteed

screen shot 2016-12-10 at 6 00 51 pm
@AndrewJDR
Copy link
Collaborator

AndrewJDR commented Dec 11, 2016 •
edited

I believe the original imessage timestamps coming from apple are correct even though apple sends them out of order, so I presume http://matrix.org/docs/spec/application_service/unstable.html#timestamp-massaging could help with this. i.e. if it were possible to provide a origin_server_ts value, the proper message reordering would ultimately occur, even if the messages were handled by the bridge out-of-order?

Ultimately, does using origin_server_ts seem like the proper way to handle this, @ara4n @kegsay? Also see https://github.com/matrix-org/matrix-doc/issues/698

@kfatehi
Copy link
Member Author

kfatehi commented Dec 13, 2016

screen shot 2016-12-13 at 12 59 48 am

Permalink: https://matrix.to/#/!svJUttHBtRMdXmEhEy:matrix.org/$1481587717845894gPUre:matrix.org

kfatehi added a commit that referenced this issue May 13, 2017
@kfatehi
add scripts that help test #1 and #2
d0e0a5e 
message order produced by transcript reader does not make a difference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kfatehi @AndrewJDR