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.

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

Timestamp massaging for application services #1585

Open
turt2live opened this Issue Aug 28, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@turt2live
Copy link
Member

turt2live commented Aug 28, 2018

This needs a bit of thought before it can safely be in the spec. The intention behind timestamp massaging is that appservices can bridge in old history for a network into matrix seamlessly. The ?ts param is meant to apply to every endpoint that sends an event, such as /send, /ban, and /createRoom. the last one in that list, /createRoom, causes some problems though: the ?ts param seems too blunt to apply to all of the events in the request.

In addition, the section needs some work in terms of wording to reference that the ?ts param does not affect DAG ordering.

For reference, here's the original section: https://github.com/matrix-org/matrix-doc/blob/17e0ef4b91034b0cdb010416225ffac65b4107fc/specification/application_service_api.rst#232timestamp-massaging

@turt2live turt2live added the feature label Aug 28, 2018

turt2live added a commit to turt2live/matrix-doc that referenced this issue Aug 28, 2018

@turt2live

This comment has been minimized.

Copy link
Member

turt2live commented Aug 29, 2018

See also: #1394 (closed in favour of this)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment